Yellowfin 9 , Rest API Security token is invalid.

Sachin Lalwani shared this question 14 days ago
In Progress

i am referring the below given url.


https://wiki.yellowfinbi.com/display/yfcurrent/REST+API


I am using Yellowfin 9. Using postman , i performed an experiment.


webservice - http://YFip:YFPort/mdp/api/refresh-tokens


i added below given required headers .


Authorization : YELLOWFIN ts=1600224140615 nonce=3370ddc4-37d9-41b9-9f24-ada181fdc4bf token=....

Content-Type: application/json

Accept:applcation/vnd.yellowfin.api-v1+json


within body -


{

"username" : "user1@domain.com" ,

"password" : "password" ,

"clientOrgRef" : "org1" ,

}


Question about security token -

In order to call any web service , security token is required.

How and from where to obtain security token ?


On one of our server , we have oauth2 installed and working.

Can i pickup any token of oauth2 and try it in yellowfin?


In my opinion, yellowfin will accept only those tokens which are generated by yellowfin itself and not by other system.


Since , I am not supplying correct token, Hence i am receiving json response Invalid credential.

Please assist.

Comments (22)

photo
1

Hi Sachin,

Security tokens are part of the response when creating access tokens in our API documentation. The documentation can be found here: REST API - Yellowfin Guide 9 - Global Site (yellowfinbi.com)

There's a section on Web SSO in the Wiki. It also covers using the security token gained from that to use with the JsAPI: REST API - Yellowfin Guide 9 - Global Site (yellowfinbi.com)

And our developer Wiki goes into creating Access Tokens and their security token responses in more detail here: ReDoc (yellowfinbi.com)

Let me know if the above documentation helps answer your question.

Kind regards,

Chris

photo
1

Hi Chris,


Appreciate your response .

I followed the document and also tried calling - /login-tokens/create-sso-token api.

Every time I tried , getting response - {"code":401,"reason":"INVALID_CREDENTIALS"}

Seems like something is still missing in the configuration.

Please refer attached screen print for further details.


Could you please let me know if there are any prerequisite to enable API or any configuration changes needed.

Would it be also possible to share working example along with the detailed documentation on Authorization header , specially the purpose of specifying random UUID in nonce .

photo
1

Hi Sachin,

I've gone through this for you and have an example below. Please note that you have a comma missing from your authorisation header, which is likely why you are encountering this error.

It should be: YELLOWFIN ts=1556165938563, nonce=123

/eae7caf3ac618087f9e11d4383345b31

/81b9b03c709a990baf97094668057eb3

/1bd92790857ca66c331c15bbca401527

The random UUID is likely used as an extra layer of security to hash or salt the credentials.

Kind regards,

Chris

photo
1

Hi Chris,

Appreciate your response .

I have followed the approach as shown in your reply but still not able to receive the success response.

This may be due to some different reason.

Can we set up a call ? I would like to know which configuration part I am missing ?


Regards,

Sachin

photo
1

Hi Sachin,

Did you add the ',' comma to your authorisation header?

Did that change the error message return or are you getting the same one?

The nonce can be any value but the ts must be a current or near current value.

There must be a comma separating them.

I might have to put you in touch with the consulting team when it comes to REST api integration if that is still not working.

Kind regards,

Chris

photo
photo
1

Hi Chris,

Thanks for your quick response. We tried adding a comma but issue still persist.

It would be a great help if we can connect with the Yellowfin consulting team for further help.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 24 February 2021 09:48 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hi Sachin,

That's no worries. Would you mind sending over a couple of new screenshots to pass on to the team so they can have a look.

Kind regards,

Chris

photo
1

Please find below given screen prints.

0a63d3a5e8988bc01d8f04454d6e5e7a

5dd733042ea114a6a4876ffc4716f856

b531d75535b2c4c7192658aa93924be6

4f5e14ae64547610fc36001dfd7977db

6da384079b504b13482c8d0e25922ba9

Regards,

Bhushan Mahajan

From: Sachin Lalwani

Sent: Wednesday, February 24, 2021 10:16 PM

To: Yellowfin Support

Cc: Bhushan N. Mahajan; Ashley Riggle

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Chris,

Thanks for your quick response. We tried adding a comma but issue still persist.

It would be a great help if we can connect with the Yellowfin consulting team for further help.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 24 February 2021 09:48 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hi Sachin and Bhushan,

I hope you both are doing well!

As Chris explained in the ticket, it sounds like your questions will be better addressed with our consulting team. As you do have access to our team via 4 Extended Services hours per month, I’ve included the ESNA@yellowfin.bi consulting group in this response, and someone from our consulting team will be reaching out to you shortly for assistance.

Please let me know if there is anything else I can do to help at this point!

Best,

Ashley

Ashley Riggle   /   Customer Success Manager

ashley.riggle@yellowfin.bi  / (844) 424-5678 ext. 123

110 Lindsay Cir, Suite A, Ketchum, ID 83340

fb2e0887aaf98b9c992f64836420c22b

33eaeb4f501c116f8cb8a6c93b77edaca1a09cc4cf600155f9a2be153407470ec78dd9895c59bb07c00273169a7dee4e0d0f32eee8471f347e7775eb6b743162

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: "Bhushan N. Mahajan" <Bhushan.Mahajan@majesco.com>

Date: Wednesday, February 24, 2021 at 12:35 PM

To: Sachin Lalwani <Sachin.Lalwani@majesco.com>, Support Queue <support@Yellowfin.bi>

Cc: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Please find below given screen prints.

Regards,

Bhushan Mahajan

From: Sachin Lalwani

Sent: Wednesday, February 24, 2021 10:16 PM

To: Yellowfin Support

Cc: Bhushan N. Mahajan; Ashley Riggle

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Chris,

Thanks for your quick response. We tried adding a comma but issue still persist.

It would be a great help if we can connect with the Yellowfin consulting team for further help.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 24 February 2021 09:48 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hello,

                I’ve taken a look at the screenshots below.

The typical workflow for using the /login-tokens call is as such:

  1. Use /refresh-tokens to request a refresh token
  2. Pass the refresh token into the TOKEN parameter of a /access-tokens request
  3. /login-tokens; pass the access token into the TOKEN parameter of your /login-tokens request

In your screenshot below, I do not see any TOKEN parameter in your ‘Authorization’ Header. (unless it is cut-off, or I’m mistaken)

I’ve attached an export from my own POSTMAN of example API calls (including all three ‘token’ calls) I make from my localhost environment you can try reverse-engineering.

Let us know if that helps. Thanks.

0a94452770b1be03749beef78e916156

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

971506c241a9ef9d6c656df7f8f8b4e518a4ac07e767bccfb8fcce10a147f346ee5ac3ccb41fe98215b1d5f107c13e51be501f35ece05b74e6fde57adb3c4655

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Sent: Wednesday, February 24, 2021 4:02 PM

To: Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Sachin Lalwani <Sachin.Lalwani@majesco.com>; Support Queue <support@Yellowfin.bi>

Cc: Extended Services NA <esna@Yellowfin.bi>

Subject: Re: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Sachin and Bhushan,

I hope you both are doing well!

As Chris explained in the ticket, it sounds like your questions will be better addressed with our consulting team. As you do have access to our team via 4 Extended Services hours per month, I’ve included the ESNA@yellowfin.bi consulting group in this response, and someone from our consulting team will be reaching out to you shortly for assistance.

Please let me know if there is anything else I can do to help at this point!

Best,

Ashley

Ashley Riggle   /   Customer Success Manager

ashley.riggle@yellowfin.bi  / (844) 424-5678 ext. 123

110 Lindsay Cir, Suite A, Ketchum, ID 83340

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: "Bhushan N. Mahajan" <Bhushan.Mahajan@majesco.com>

Date: Wednesday, February 24, 2021 at 12:35 PM

To: Sachin Lalwani <Sachin.Lalwani@majesco.com>, Support Queue <support@Yellowfin.bi>

Cc: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Please find below given screen prints.

Regards,

Bhushan Mahajan

From: Sachin Lalwani

Sent: Wednesday, February 24, 2021 10:16 PM

To: Yellowfin Support

Cc: Bhushan N. Mahajan; Ashley Riggle

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Chris,

Thanks for your quick response. We tried adding a comma but issue still persist.

It would be a great help if we can connect with the Yellowfin consulting team for further help.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 24 February 2021 09:48 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hello,

                Just an amendment to my previous email. Just realized you are trying to use the /login-tokens/create-sso-token call (the one without a valid Access Token).

Perhaps what I’ve sent just now does not apply to your use-case.

Are you able to send me an export of your call in POSTMAN as well? I can test it out in my environment and see if I can find anything.

Thanks.

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

79b71bc178a6ebc439e8f7607f3315a02e92b37a77d8f7094a6ebbaf6c807a4e997037faedb0155af30ba2052ccd0d110b0fdc29460d7f5a220a6b739ab5b364d3353170a0b04658ac6a6559ea120781

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Ashwin Nelluri

Sent: Wednesday, February 24, 2021 5:19 PM

To: Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Sachin Lalwani <Sachin.Lalwani@majesco.com>

Cc: Extended Services NA <esna@Yellowfin.bi>; Ashley Riggle <ashley.riggle@Yellowfin.bi>; Support Queue <support@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hello,

                I’ve taken a look at the screenshots below.

The typical workflow for using the /login-tokens call is as such:

  1. Use /refresh-tokens to request a refresh token
  2. Pass the refresh token into the TOKEN parameter of a /access-tokens request
  3. /login-tokens; pass the access token into the TOKEN parameter of your /login-tokens request

In your screenshot below, I do not see any TOKEN parameter in your ‘Authorization’ Header. (unless it is cut-off, or I’m mistaken)

I’ve attached an export from my own POSTMAN of example API calls (including all three ‘token’ calls) I make from my localhost environment you can try reverse-engineering.

Let us know if that helps. Thanks.

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Sent: Wednesday, February 24, 2021 4:02 PM

To: Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Sachin Lalwani <Sachin.Lalwani@majesco.com>; Support Queue <support@Yellowfin.bi>

Cc: Extended Services NA <esna@Yellowfin.bi>

Subject: Re: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Sachin and Bhushan,

I hope you both are doing well!

As Chris explained in the ticket, it sounds like your questions will be better addressed with our consulting team. As you do have access to our team via 4 Extended Services hours per month, I’ve included the ESNA@yellowfin.bi consulting group in this response, and someone from our consulting team will be reaching out to you shortly for assistance.

Please let me know if there is anything else I can do to help at this point!

Best,

Ashley

Ashley Riggle   /   Customer Success Manager

ashley.riggle@yellowfin.bi  / (844) 424-5678 ext. 123

110 Lindsay Cir, Suite A, Ketchum, ID 83340

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: "Bhushan N. Mahajan" <Bhushan.Mahajan@majesco.com>

Date: Wednesday, February 24, 2021 at 12:35 PM

To: Sachin Lalwani <Sachin.Lalwani@majesco.com>, Support Queue <support@Yellowfin.bi>

Cc: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Please find below given screen prints.

Regards,

Bhushan Mahajan

From: Sachin Lalwani

Sent: Wednesday, February 24, 2021 10:16 PM

To: Yellowfin Support

Cc: Bhushan N. Mahajan; Ashley Riggle

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Chris,

Thanks for your quick response. We tried adding a comma but issue still persist.

It would be a great help if we can connect with the Yellowfin consulting team for further help.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 24 February 2021 09:48 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hello,

                One more update, can you try adding commas between your userName and password elements in the body? Like mine below?

if this doesn’t work for you, happy to schedule a quick call to screenshare.

Typically 401 – INVALID CREDENTIALS has to do with referencing an incorrect user in my experience.

Worth considering: username values are case-sensitive in Yellowfin. Worth validating the corresponding record in the Yellowfin config db (check the ipclass table to compare ‘Email Left’ and ‘Email Right’ columns with your provided username)

Just for proof, I submitted the below in my environment (create-sso-token call), and found it to return a valid token response:

Request

d3c3cb7facf616e7de0c4582e1d637cc

Headers

da248b8efda8e206064efb59eba12af5

Response

9541815421b11d01b90943a97bd59f1f

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

59578edb6aa8c5431ad451679ebca6e41e1cad126730b429d27a7214b84dcfa0

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Ashwin Nelluri

Sent: Wednesday, February 24, 2021 5:25 PM

To: Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Sachin Lalwani <Sachin.Lalwani@majesco.com>

Cc: Extended Services NA <esna@Yellowfin.bi>; Ashley Riggle <ashley.riggle@Yellowfin.bi>; Support Queue <support@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hello,

                Just an amendment to my previous email. Just realized you are trying to use the /login-tokens/create-sso-token call (the one without a valid Access Token).

Perhaps what I’ve sent just now does not apply to your use-case.

Are you able to send me an export of your call in POSTMAN as well? I can test it out in my environment and see if I can find anything.

Thanks.

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Ashwin Nelluri

Sent: Wednesday, February 24, 2021 5:19 PM

To: Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Sachin Lalwani <Sachin.Lalwani@majesco.com>

Cc: Extended Services NA <esna@Yellowfin.bi>; Ashley Riggle <ashley.riggle@Yellowfin.bi>; Support Queue <support@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hello,

                I’ve taken a look at the screenshots below.

The typical workflow for using the /login-tokens call is as such:

  1. Use /refresh-tokens to request a refresh token
  2. Pass the refresh token into the TOKEN parameter of a /access-tokens request
  3. /login-tokens; pass the access token into the TOKEN parameter of your /login-tokens request

In your screenshot below, I do not see any TOKEN parameter in your ‘Authorization’ Header. (unless it is cut-off, or I’m mistaken)

I’ve attached an export from my own POSTMAN of example API calls (including all three ‘token’ calls) I make from my localhost environment you can try reverse-engineering.

Let us know if that helps. Thanks.

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Sent: Wednesday, February 24, 2021 4:02 PM

To: Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Sachin Lalwani <Sachin.Lalwani@majesco.com>; Support Queue <support@Yellowfin.bi>

Cc: Extended Services NA <esna@Yellowfin.bi>

Subject: Re: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Sachin and Bhushan,

I hope you both are doing well!

As Chris explained in the ticket, it sounds like your questions will be better addressed with our consulting team. As you do have access to our team via 4 Extended Services hours per month, I’ve included the ESNA@yellowfin.bi consulting group in this response, and someone from our consulting team will be reaching out to you shortly for assistance.

Please let me know if there is anything else I can do to help at this point!

Best,

Ashley

Ashley Riggle   /   Customer Success Manager

ashley.riggle@yellowfin.bi  / (844) 424-5678 ext. 123

110 Lindsay Cir, Suite A, Ketchum, ID 83340

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: "Bhushan N. Mahajan" <Bhushan.Mahajan@majesco.com>

Date: Wednesday, February 24, 2021 at 12:35 PM

To: Sachin Lalwani <Sachin.Lalwani@majesco.com>, Support Queue <support@Yellowfin.bi>

Cc: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Please find below given screen prints.

Regards,

Bhushan Mahajan

From: Sachin Lalwani

Sent: Wednesday, February 24, 2021 10:16 PM

To: Yellowfin Support

Cc: Bhushan N. Mahajan; Ashley Riggle

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Chris,

Thanks for your quick response. We tried adding a comma but issue still persist.

It would be a great help if we can connect with the Yellowfin consulting team for further help.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 24 February 2021 09:48 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hi Ashwin ,

Here , I am using the json , which you have provided.

While calling /api  , I  am receiving invalid credentials response .

I  am receiving same respone while calling  -

/api/refresh-tokens

 /api/access-tokens  ,

api/login-tokens

Not sure about where is the issue?

Can we set up  a   webex meeting so that I can   demonstrate  this issue  ?

02d743579a377e5376b812262bb9847c 

573a7694123854511df75582497c2ceeca8bd5499418e999fd54fb2faf0b60d5

From: Ashwin Nelluri [mailto:Ashwin.Nelluri@Yellowfin.bi]

Sent: Thursday, February 25, 2021 3:55 AM

To: Bhushan N. Mahajan; Sachin Lalwani

Cc: Extended Services NA; Ashley Riggle; Support Queue

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

Hello,

                Just an amendment to my previous email. Just realized you are trying to use the /login-tokens/create-sso-token call (the one without a valid Access Token).

Perhaps what I’ve sent just now does not apply to your use-case.

Are you able to send me an export of your call in POSTMAN as well? I can test it out in my environment and see if I can find anything.

Thanks.

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

aed0505d4e665eae7fee35a00d838a889244a178feb0b3307475d9be31221009

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Ashwin Nelluri

Sent: Wednesday, February 24, 2021 5:19 PM

To: Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Sachin Lalwani <Sachin.Lalwani@majesco.com>

Cc: Extended Services NA <esna@Yellowfin.bi>; Ashley Riggle <ashley.riggle@Yellowfin.bi>; Support Queue <support@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hello,

                I’ve taken a look at the screenshots below.

The typical workflow for using the /login-tokens call is as such:

1.)Use /refresh-tokens to request a refresh token

2.)Pass the refresh token into the TOKEN parameter of a /access-tokens request

3.)/login-tokens; pass the access token into the TOKEN parameter of your /login-tokens request

In your screenshot below, I do not see any TOKEN parameter in your ‘Authorization’ Header. (unless it is cut-off, or I’m mistaken)

I’ve attached an export from my own POSTMAN of example API calls (including all three ‘token’ calls) I make from my localhost environment you can try reverse-engineering.

Let us know if that helps. Thanks.

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Sent: Wednesday, February 24, 2021 4:02 PM

To: Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Sachin Lalwani <Sachin.Lalwani@majesco.com>; Support Queue <support@Yellowfin.bi>

Cc: Extended Services NA <esna@Yellowfin.bi>

Subject: Re: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Sachin and Bhushan,

I hope you both are doing well!

As Chris explained in the ticket, it sounds like your questions will be better addressed with our consulting team. As you do have access to our team via 4 Extended Services hours per month, I’ve included the ESNA@yellowfin.bi consulting group in this response, and someone from our consulting team will be reaching out to you shortly for assistance.

Please let me know if there is anything else I can do to help at this point!

Best,

Ashley

Ashley Riggle   /   Customer Success Manager

ashley.riggle@yellowfin.bi  / (844) 424-5678 ext. 123

110 Lindsay Cir, Suite A, Ketchum, ID 83340

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: "Bhushan N. Mahajan" <Bhushan.Mahajan@majesco.com>

Date: Wednesday, February 24, 2021 at 12:35 PM

To: Sachin Lalwani <Sachin.Lalwani@majesco.com>, Support Queue <support@Yellowfin.bi>

Cc: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Please find below given screen prints.

Regards,

Bhushan Mahajan

From: Sachin Lalwani

Sent: Wednesday, February 24, 2021 10:16 PM

To: Yellowfin Support

Cc: Bhushan N. Mahajan; Ashley Riggle

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Chris,

Thanks for your quick response. We tried adding a comma but issue still persist.

It would be a great help if we can connect with the Yellowfin consulting team for further help.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 24 February 2021 09:48 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hi Ashley,

Thanks for looping-in the consulting team. We haven’t received any response from anyone so far. Would it be possible to expedite the request? We are building a use case to embedded the Yellowfin Story and Signals within the Majesco suite.

Enjoy the weekend, and stay safe

Thanks, Sachin

From: Ashley Riggle [mailto:ashley.riggle@Yellowfin.bi]

Sent: 25 February 2021 02:32 AM

To: Bhushan N. Mahajan; Sachin Lalwani; Support Queue

Cc: Extended Services NA

Subject: Re: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

Hi Sachin and Bhushan,

I hope you both are doing well!

As Chris explained in the ticket, it sounds like your questions will be better addressed with our consulting team. As you do have access to our team via 4 Extended Services hours per month, I’ve included the ESNA@yellowfin.bi consulting group in this response, and someone from our consulting team will be reaching out to you shortly for assistance.

Please let me know if there is anything else I can do to help at this point!

Best,

Ashley

Ashley Riggle   /   Customer Success Manager

ashley.riggle@yellowfin.bi  / (844) 424-5678 ext. 123

110 Lindsay Cir, Suite A, Ketchum, ID 83340

9eae2ec7cb7563a1a1059c1e576c19bf

90f6e6f59486e3c24f68eda577cf79b99f92d375a514bd997b5f7b2ef9fc3f84995593c48623dd48bdf2ef19ad8c17c42b45f924c88d99efaf6ccdf41524b329

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: "Bhushan N. Mahajan" <Bhushan.Mahajan@majesco.com>

Date: Wednesday, February 24, 2021 at 12:35 PM

To: Sachin Lalwani <Sachin.Lalwani@majesco.com>, Support Queue <support@Yellowfin.bi>

Cc: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Please find below given screen prints.

Regards,

Bhushan Mahajan

From: Sachin Lalwani

Sent: Wednesday, February 24, 2021 10:16 PM

To: Yellowfin Support

Cc: Bhushan N. Mahajan; Ashley Riggle

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Chris,

Thanks for your quick response. We tried adding a comma but issue still persist.

It would be a great help if we can connect with the Yellowfin consulting team for further help.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 24 February 2021 09:48 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hi Sachin,

Ashwin has replied below if you want to take a look.

Kind regards,

Chris

photo
1

Hey Chris,

Somehow I don’t see any latest response from Ashwin. Last was on 02/24 05:19 PM.

We tried one more time but the issue still persist.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 26 February 2021 09:51 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hi Sachin,

Please check the thread on our Community page, available here: Yellowfin 9 , Rest API Security token is invalid. | Community (yellowfinbi.com)

All the responses are collated there.

Kind regards,

Chris

photo
1

Hi Chris,

Thanks for your response. We appreciate all your help.

Just to reiterate, we have tried all possible combinations including recommendations from Ashwin. Can we have someone from the consulting team to help us on a priority.

Ashley, Hope you had a good long weekend. I need your help. Would it be possible to expedite the request. We have a demo where are we intend to show case embedded reports within Majesco suite environment.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 01 March 2021 10:51 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hi Sachin,

Thank you for your update, I have reached out to my consultant team and requested that they provide their available times for a call with you to address the issue at hand. When is your demo to share the embedded reports?

If you don’t receive a response from our consultant team, please let me know, and I can provide further assistance.

Best,

Ashley

Ashley Riggle   /   Customer Success Manager

ashley.riggle@yellowfin.bi  / (844) 424-5678 ext. 123

110 Lindsay Cir, Suite A, Ketchum, ID 83340

d18dc1feea337446459044d2c8c135fd

57c93ee5fbac7558f4663af2eb262a186bcb61b8eedca1406f0fb87916cd0ad25b0bddc3e6d7059fd9e7d5cefe9fe22ef690a0e1d0546d127681bc9b5c2eea84

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Sachin Lalwani <Sachin.Lalwani@majesco.com>

Date: Monday, March 1, 2021 at 10:30 AM

To: Support Queue <support@Yellowfin.bi>

Cc: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Chris,

Thanks for your response. We appreciate all your help.

Just to reiterate, we have tried all possible combinations including recommendations from Ashwin. Can we have someone from the consulting team to help us on a priority.

Ashley, Hope you had a good long weekend. I need your help. Would it be possible to expedite the request. We have a demo where are we intend to show case embedded reports within Majesco suite environment.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 01 March 2021 10:51 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hi Sachin/Bhushan,

                Are you available this afternoon to hop on a quick call? Let me know I’ll send over a RingCentral.

Thanks.

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

7903aa3939c348302cecf78802d80d425b1b8149d04017867e6d434ee3f497f7537f6ef63a9f574553402700541304fd487fd38319cdd22b5aebc80c2621c5b58fa1179f3b59c29b0100e6fd94525dbb

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Sachin Lalwani <Sachin.Lalwani@majesco.com>

Sent: Friday, February 26, 2021 9:36 AM

To: Ashley Riggle <ashley.riggle@Yellowfin.bi>; Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Support Queue <support@Yellowfin.bi>

Cc: Extended Services NA <esna@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Ashley,

Thanks for looping-in the consulting team. We haven’t received any response from anyone so far. Would it be possible to expedite the request? We are building a use case to embedded the Yellowfin Story and Signals within the Majesco suite.

Enjoy the weekend, and stay safe

Thanks, Sachin

From: Ashley Riggle [mailto:ashley.riggle@Yellowfin.bi]

Sent: 25 February 2021 02:32 AM

To: Bhushan N. Mahajan; Sachin Lalwani; Support Queue

Cc: Extended Services NA

Subject: Re: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

Hi Sachin and Bhushan,

I hope you both are doing well!

As Chris explained in the ticket, it sounds like your questions will be better addressed with our consulting team. As you do have access to our team via 4 Extended Services hours per month, I’ve included the ESNA@yellowfin.bi consulting group in this response, and someone from our consulting team will be reaching out to you shortly for assistance.

Please let me know if there is anything else I can do to help at this point!

Best,

Ashley

Ashley Riggle   /   Customer Success Manager

ashley.riggle@yellowfin.bi  / (844) 424-5678 ext. 123

110 Lindsay Cir, Suite A, Ketchum, ID 83340

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: "Bhushan N. Mahajan" <Bhushan.Mahajan@majesco.com>

Date: Wednesday, February 24, 2021 at 12:35 PM

To: Sachin Lalwani <Sachin.Lalwani@majesco.com>, Support Queue <support@Yellowfin.bi>

Cc: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Please find below given screen prints.

Regards,

Bhushan Mahajan

From: Sachin Lalwani

Sent: Wednesday, February 24, 2021 10:16 PM

To: Yellowfin Support

Cc: Bhushan N. Mahajan; Ashley Riggle

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Chris,

Thanks for your quick response. We tried adding a comma but issue still persist.

It would be a great help if we can connect with the Yellowfin consulting team for further help.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 24 February 2021 09:48 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hi Ashwin,

We are based out of India. Would it possible to setup call anytime between 08:00 AM to 11:00AM EST?

Thanks, Sachin

From: Ashwin Nelluri [mailto:Ashwin.Nelluri@Yellowfin.bi]

Sent: 02 March 2021 01:21 AM

To: Sachin Lalwani; Ashley Riggle; Bhushan N. Mahajan; Support Queue

Cc: Extended Services NA

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

Hi Sachin/Bhushan,

                Are you available this afternoon to hop on a quick call? Let me know I’ll send over a RingCentral.

Thanks.

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

8cec95bde9f9e83d3f8e2ecb244d173fa37290ae6556d693fecf7a58d11f8aac6d42fee26ccf3f8dd113adafa7f7360f9bd90f1b6acc718ac589dd1d7cb3309e57a7609ecb95c7dabd5727fd79b770d9

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Sachin Lalwani <Sachin.Lalwani@majesco.com>

Sent: Friday, February 26, 2021 9:36 AM

To: Ashley Riggle <ashley.riggle@Yellowfin.bi>; Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Support Queue <support@Yellowfin.bi>

Cc: Extended Services NA <esna@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Ashley,

Thanks for looping-in the consulting team. We haven’t received any response from anyone so far. Would it be possible to expedite the request? We are building a use case to embedded the Yellowfin Story and Signals within the Majesco suite.

Enjoy the weekend, and stay safe

Thanks, Sachin

From: Ashley Riggle [mailto:ashley.riggle@Yellowfin.bi]

Sent: 25 February 2021 02:32 AM

To: Bhushan N. Mahajan; Sachin Lalwani; Support Queue

Cc: Extended Services NA

Subject: Re: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

Hi Sachin and Bhushan,

I hope you both are doing well!

As Chris explained in the ticket, it sounds like your questions will be better addressed with our consulting team. As you do have access to our team via 4 Extended Services hours per month, I’ve included the ESNA@yellowfin.bi consulting group in this response, and someone from our consulting team will be reaching out to you shortly for assistance.

Please let me know if there is anything else I can do to help at this point!

Best,

Ashley

Ashley Riggle   /   Customer Success Manager

ashley.riggle@yellowfin.bi  / (844) 424-5678 ext. 123

110 Lindsay Cir, Suite A, Ketchum, ID 83340

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: "Bhushan N. Mahajan" <Bhushan.Mahajan@majesco.com>

Date: Wednesday, February 24, 2021 at 12:35 PM

To: Sachin Lalwani <Sachin.Lalwani@majesco.com>, Support Queue <support@Yellowfin.bi>

Cc: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Please find below given screen prints.

Regards,

Bhushan Mahajan

From: Sachin Lalwani

Sent: Wednesday, February 24, 2021 10:16 PM

To: Yellowfin Support

Cc: Bhushan N. Mahajan; Ashley Riggle

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Chris,

Thanks for your quick response. We tried adding a comma but issue still persist.

It would be a great help if we can connect with the Yellowfin consulting team for further help.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 24 February 2021 09:48 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hello,

                I’m available for the next hour or so if you’d like to meet. Otherwise I’ll schedule something for us tomorrow during the time window.

Thanks.

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

a08ab2bcecb1132b794883376f21880094fbf63f2dbfad98280b9fd77cd4829c07cb55bcbcdd44f6eb595071260d5d841f5043859c00c9e719e565f0507d65578d059fbfef316d04ef6ba543b26f84ea

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Sachin Lalwani <Sachin.Lalwani@majesco.com>

Sent: Tuesday, March 2, 2021 12:48 AM

To: Ashwin Nelluri <Ashwin.Nelluri@Yellowfin.bi>; Ashley Riggle <ashley.riggle@Yellowfin.bi>; Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Support Queue <support@Yellowfin.bi>

Cc: Extended Services NA <esna@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Ashwin,

We are based out of India. Would it possible to setup call anytime between 08:00 AM to 11:00AM EST?

Thanks, Sachin

From: Ashwin Nelluri [mailto:Ashwin.Nelluri@Yellowfin.bi]

Sent: 02 March 2021 01:21 AM

To: Sachin Lalwani; Ashley Riggle; Bhushan N. Mahajan; Support Queue

Cc: Extended Services NA

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

Hi Sachin/Bhushan,

                Are you available this afternoon to hop on a quick call? Let me know I’ll send over a RingCentral.

Thanks.

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Sachin Lalwani <Sachin.Lalwani@majesco.com>

Sent: Friday, February 26, 2021 9:36 AM

To: Ashley Riggle <ashley.riggle@Yellowfin.bi>; Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Support Queue <support@Yellowfin.bi>

Cc: Extended Services NA <esna@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Ashley,

Thanks for looping-in the consulting team. We haven’t received any response from anyone so far. Would it be possible to expedite the request? We are building a use case to embedded the Yellowfin Story and Signals within the Majesco suite.

Enjoy the weekend, and stay safe

Thanks, Sachin

From: Ashley Riggle [mailto:ashley.riggle@Yellowfin.bi]

Sent: 25 February 2021 02:32 AM

To: Bhushan N. Mahajan; Sachin Lalwani; Support Queue

Cc: Extended Services NA

Subject: Re: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

Hi Sachin and Bhushan,

I hope you both are doing well!

As Chris explained in the ticket, it sounds like your questions will be better addressed with our consulting team. As you do have access to our team via 4 Extended Services hours per month, I’ve included the ESNA@yellowfin.bi consulting group in this response, and someone from our consulting team will be reaching out to you shortly for assistance.

Please let me know if there is anything else I can do to help at this point!

Best,

Ashley

Ashley Riggle   /   Customer Success Manager

ashley.riggle@yellowfin.bi  / (844) 424-5678 ext. 123

110 Lindsay Cir, Suite A, Ketchum, ID 83340

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: "Bhushan N. Mahajan" <Bhushan.Mahajan@majesco.com>

Date: Wednesday, February 24, 2021 at 12:35 PM

To: Sachin Lalwani <Sachin.Lalwani@majesco.com>, Support Queue <support@Yellowfin.bi>

Cc: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Please find below given screen prints.

Regards,

Bhushan Mahajan

From: Sachin Lalwani

Sent: Wednesday, February 24, 2021 10:16 PM

To: Yellowfin Support

Cc: Bhushan N. Mahajan; Ashley Riggle

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Chris,

Thanks for your quick response. We tried adding a comma but issue still persist.

It would be a great help if we can connect with the Yellowfin consulting team for further help.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 24 February 2021 09:48 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hey Ashwin,

Thanks a lot for your quick response. Can we meet at 09:30 AM EST? i.e in next 18 mins.

Thanks, Sachin

From: Ashwin Nelluri [mailto:Ashwin.Nelluri@Yellowfin.bi]

Sent: 02 March 2021 07:37 PM

To: Sachin Lalwani; Ashley Riggle; Bhushan N. Mahajan; Support Queue

Cc: Extended Services NA

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

Hello,

                I’m available for the next hour or so if you’d like to meet. Otherwise I’ll schedule something for us tomorrow during the time window.

Thanks.

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

50efcc0aee167d7d8b36fe3a2efb27354468b1db6d7785305cb4a3877c3e5785e2e3550287436192d9bb729010795a1b9fae61c29fc73a7ad3f0dd90c04c3508ef20112d76b420dc3d1b1a2060f9dbf9

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Sachin Lalwani <Sachin.Lalwani@majesco.com>

Sent: Tuesday, March 2, 2021 12:48 AM

To: Ashwin Nelluri <Ashwin.Nelluri@Yellowfin.bi>; Ashley Riggle <ashley.riggle@Yellowfin.bi>; Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Support Queue <support@Yellowfin.bi>

Cc: Extended Services NA <esna@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Ashwin,

We are based out of India. Would it possible to setup call anytime between 08:00 AM to 11:00AM EST?

Thanks, Sachin

From: Ashwin Nelluri [mailto:Ashwin.Nelluri@Yellowfin.bi]

Sent: 02 March 2021 01:21 AM

To: Sachin Lalwani; Ashley Riggle; Bhushan N. Mahajan; Support Queue

Cc: Extended Services NA

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

Hi Sachin/Bhushan,

                Are you available this afternoon to hop on a quick call? Let me know I’ll send over a RingCentral.

Thanks.

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Sachin Lalwani <Sachin.Lalwani@majesco.com>

Sent: Friday, February 26, 2021 9:36 AM

To: Ashley Riggle <ashley.riggle@Yellowfin.bi>; Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Support Queue <support@Yellowfin.bi>

Cc: Extended Services NA <esna@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Ashley,

Thanks for looping-in the consulting team. We haven’t received any response from anyone so far. Would it be possible to expedite the request? We are building a use case to embedded the Yellowfin Story and Signals within the Majesco suite.

Enjoy the weekend, and stay safe

Thanks, Sachin

From: Ashley Riggle [mailto:ashley.riggle@Yellowfin.bi]

Sent: 25 February 2021 02:32 AM

To: Bhushan N. Mahajan; Sachin Lalwani; Support Queue

Cc: Extended Services NA

Subject: Re: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

Hi Sachin and Bhushan,

I hope you both are doing well!

As Chris explained in the ticket, it sounds like your questions will be better addressed with our consulting team. As you do have access to our team via 4 Extended Services hours per month, I’ve included the ESNA@yellowfin.bi consulting group in this response, and someone from our consulting team will be reaching out to you shortly for assistance.

Please let me know if there is anything else I can do to help at this point!

Best,

Ashley

Ashley Riggle   /   Customer Success Manager

ashley.riggle@yellowfin.bi  / (844) 424-5678 ext. 123

110 Lindsay Cir, Suite A, Ketchum, ID 83340

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: "Bhushan N. Mahajan" <Bhushan.Mahajan@majesco.com>

Date: Wednesday, February 24, 2021 at 12:35 PM

To: Sachin Lalwani <Sachin.Lalwani@majesco.com>, Support Queue <support@Yellowfin.bi>

Cc: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Please find below given screen prints.

Regards,

Bhushan Mahajan

From: Sachin Lalwani

Sent: Wednesday, February 24, 2021 10:16 PM

To: Yellowfin Support

Cc: Bhushan N. Mahajan; Ashley Riggle

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Chris,

Thanks for your quick response. We tried adding a comma but issue still persist.

It would be a great help if we can connect with the Yellowfin consulting team for further help.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 24 February 2021 09:48 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hi Sachin,

Were you able to meeting with Ashwin and get this resolved?

Kind regards,

Chris

photo
1

Hello Chris,

We met Chris a day before and the issue is resolved. Somehow the TS parameter was not defined correctly.

Please feel free to close the ticket. Thanks a lot for all your help.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 04 March 2021 12:15 AM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

photo
1

Hey Ashwin,

Appreciate your time in helping us resolving the issue. I must say the call was very informative. We have successfully tested your suggestions and able to generate the token.

I’ve one suggestion, can we request Yellowfin technical team to add / update developer guide to include some examples including details on TS parameter and workflow. This might be helpful for other customer.

Thanks again.

Sachin

From: Ashwin Nelluri [mailto:Ashwin.Nelluri@Yellowfin.bi]

Sent: 02 March 2021 07:37 PM

To: Sachin Lalwani; Ashley Riggle; Bhushan N. Mahajan; Support Queue

Cc: Extended Services NA

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

Hello,

                I’m available for the next hour or so if you’d like to meet. Otherwise I’ll schedule something for us tomorrow during the time window.

Thanks.

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

5357c62ad5e4b784303d9347c1defc96b68733d9fb8245ea53a4c49b946c7bf8c487b4da91f3226c48f450af78437b60af87e3cbff67600fe94357f0dcfdd8199825a7d55d6c9d9cab627c05776ac4f6

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Sachin Lalwani <Sachin.Lalwani@majesco.com>

Sent: Tuesday, March 2, 2021 12:48 AM

To: Ashwin Nelluri <Ashwin.Nelluri@Yellowfin.bi>; Ashley Riggle <ashley.riggle@Yellowfin.bi>; Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Support Queue <support@Yellowfin.bi>

Cc: Extended Services NA <esna@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Ashwin,

We are based out of India. Would it possible to setup call anytime between 08:00 AM to 11:00AM EST?

Thanks, Sachin

From: Ashwin Nelluri [mailto:Ashwin.Nelluri@Yellowfin.bi]

Sent: 02 March 2021 01:21 AM

To: Sachin Lalwani; Ashley Riggle; Bhushan N. Mahajan; Support Queue

Cc: Extended Services NA

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

Hi Sachin/Bhushan,

                Are you available this afternoon to hop on a quick call? Let me know I’ll send over a RingCentral.

Thanks.

 

 

 

Ashwin Nelluri   /   Solution Architect

m. +1 (551) 777 2358   /   ashwin.nelluri@yellowfin.bi

Paramus, NJ, 07652

BARC – No 1. For Embedded and Operation BI.

Gartner – Ranked among the Top 5 analytics platforms across all 15 Gartner Critical Capabilities for Analytics and Business Intelligence Platforms.

Forrester – An Embedded BI Specialist. Forrester Wave.

Infotech – Enterprise BI Leader.

EMA – Leader in the use of AI, machine learning, contextual storytelling, and social communication for business intelligence.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: Sachin Lalwani <Sachin.Lalwani@majesco.com>

Sent: Friday, February 26, 2021 9:36 AM

To: Ashley Riggle <ashley.riggle@Yellowfin.bi>; Bhushan N. Mahajan <Bhushan.Mahajan@majesco.com>; Support Queue <support@Yellowfin.bi>

Cc: Extended Services NA <esna@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Ashley,

Thanks for looping-in the consulting team. We haven’t received any response from anyone so far. Would it be possible to expedite the request? We are building a use case to embedded the Yellowfin Story and Signals within the Majesco suite.

Enjoy the weekend, and stay safe

Thanks, Sachin

From: Ashley Riggle [mailto:ashley.riggle@Yellowfin.bi]

Sent: 25 February 2021 02:32 AM

To: Bhushan N. Mahajan; Sachin Lalwani; Support Queue

Cc: Extended Services NA

Subject: Re: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.

Hi Sachin and Bhushan,

I hope you both are doing well!

As Chris explained in the ticket, it sounds like your questions will be better addressed with our consulting team. As you do have access to our team via 4 Extended Services hours per month, I’ve included the ESNA@yellowfin.bi consulting group in this response, and someone from our consulting team will be reaching out to you shortly for assistance.

Please let me know if there is anything else I can do to help at this point!

Best,

Ashley

Ashley Riggle   /   Customer Success Manager

ashley.riggle@yellowfin.bi  / (844) 424-5678 ext. 123

110 Lindsay Cir, Suite A, Ketchum, ID 83340

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed.

If you have received this email in error please notify Yellowfin.

From: "Bhushan N. Mahajan" <Bhushan.Mahajan@majesco.com>

Date: Wednesday, February 24, 2021 at 12:35 PM

To: Sachin Lalwani <Sachin.Lalwani@majesco.com>, Support Queue <support@Yellowfin.bi>

Cc: Ashley Riggle <ashley.riggle@Yellowfin.bi>

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Please find below given screen prints.

Regards,

Bhushan Mahajan

From: Sachin Lalwani

Sent: Wednesday, February 24, 2021 10:16 PM

To: Yellowfin Support

Cc: Bhushan N. Mahajan; Ashley Riggle

Subject: RE: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Hi Chris,

Thanks for your quick response. We tried adding a comma but issue still persist.

It would be a great help if we can connect with the Yellowfin consulting team for further help.

Thanks, Sachin

From: Yellowfin Support [mailto:support@yellowfin.bi]

Sent: 24 February 2021 09:48 PM

To: Sachin Lalwani

Subject: New Comment in "Yellowfin 9 , Rest API Security token is invalid."

Advisory !! This email originated from a sender outside your organization. Please do not open, reply, forward, click any links or open attachments unless you know the sender, the mail ID and deem the content safe.