400 on getCustomActions with iframe embed dashboard and WAT authentication
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
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
-