Yellowfin 9 , Rest API Security token is invalid.

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

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.

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

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.

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.

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.

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.

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

Headers

Response

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: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.

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  ?

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

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.

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.

Hi Sachin,

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

Kind regards,

Chris

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.

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

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.

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

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.

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.

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.

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

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.

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

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.

Hi Sachin,

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

Kind regards,

Chris

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.

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

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.