400 on getCustomActions with iframe embed dashboard and WAT authentication

[Alexandre]

Hello,

To distribute our dashboards to our clients, we use iframes. We didn't have any issues until we started using the Web Access Token to authenticate our users. Since then, some actions in the dashboard are broken. Specifically, all actions that call the getCustomActions endpoint end with an HTTP status 400 (from blox button).

Here is an example of a response (hidden tokens)

Possibly unhandled rejection: {"data":{"error":{"code":5014,"message":"Endpoint is forbidden","status":400,"httpMessage":"Bad Request"}},"status":400,"config":{"method":"GET","transformRequest":[null],"transformResponse":[null],"jsonpCallbackParam":"callback","url":"/api/v1/blox/getCustomActions","headers":{"Internal":"true","x-request-id":"xxx","Accept":"application/json, text/plain, */*","Authorization":"xxx","Initialiser":{"words":[-408432632,967604053,-1185492005,-1736048623,-790530727,35211402,447656597,-1442048497],"sigBytes":32},"X-XSRF-TOKEN":"xxx"}},"statusText":"","xhrStatus":"complete"}

Do you have any suggestions for resolving this issue ?

Best Regards,

Alexandre

[DRay]

Hello @Alexandre,

What version of Sisense are you using? As of 2023.7 the /api/v1/getCustomActions API endpoint was deprecated and replaced with /api/v1/blox/getCustomActions.

[Alexandre]

Hello David

Thanks for your reply.

We are currently using version L2023.7.0.231 of Sisense.

It appears that we are indeed using the /api/v1/blox/getCustomActions endpoint, and we have no problem with this call when logged in with a sisense user.

It only appears when authentication is performed using the Web Access Token.

Best Regards,
Alexandre

[DRay · Accepted solution]

Hi @Alexandre,

Thank you. Looks like this was a bug that was fixed in L2023.9. 

• BloX widgets that are based on some custom actions or templates now are working as expected in the Web Access Token flow.

https://docs.sisense.com/main/SisenseLinux/l2023-9-release-notes.htm

[Alexandre]

Hello David,

Thank you for the update and for the information about the bug fix in version L2023.9.

We will be upgrading to the latest version and will let you know if the issue is resolved.

Best Regards,

Alexandre

[DRay]

Sounds good. I look forward to hearing back!

[Alexandre]

Hi David

We've upgraded and that solves our problem.

Thanks for your advice. 🙂

Best Regards,

Alexandre

[DRay]

I'm glad to hear it!