Forum Discussion

Alexandre's avatar
Alexandre
Cloud Apps
02-26-2024
Solved

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

7 Replies

Replies have been turned off for this discussion
  • DRay's avatar
    DRay
    Journey Map

    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's avatar
      Alexandre
      Cloud Apps

      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