rajatgupta - Hi team, I am facing 401 Auth issu...
Hi team, I am facing 401 Auth issue while trying to access embedded liveboard. The initial embed SDK auth calls are successful and I receive SDK_SUCCESS but later on the following calls start to fail:
Can someone please help? Added code in thread

9 Replies
We wrap ThoughtspotWrapper (which takes a flag for starting init call) over our routes:
Liveboard component:
I am able to see
onLoad
event logs
By default we have a 5 minute time for token validity. After how much time do you usually see this 401? You can increase the time in the body of the getAuthTokenWithSecret call..
Hello @rajatgupta : Set autoLogin: true in the init block of the Visual Embed SDK. This ensures that when the current token expires, the SDK will automatically generate a new token internally, preventing 401 errors due to session or token expiration. This is the recommended way to keep users logged in without manual intervention, as the SDK will handle both token expiry and idle session timeouts automatically when autoLogin is enabled Refer to https://developers.thoughtspot.com/docs/trusted-auth-sdk#_session_length for more details
Front-end trusted authentication integration
Front-end trusted authentication integration using Visual Embed SDK
this is happening within a minute; I tried increasing the validity time but still faced the same issue
I have now set
autoLogin: true
but still facing the same issueThis is my CSP visual embed host list incase it's relevant to the issue

Could it be a liveboard permission issue? I have tried accessing a liveboard which my user only has created but still the same issue.
Can you DM me the HAR file with the error? I am not able to understand if it is a permission issue or a auth issue. Has the issue been happening consistently after a minute, doesn't matter the liveboard you are viewing?
Yes, it is happening consistently. I have tried changing the liveboard as well. DM'ing HAR file.
Also, note that when I login into the cluster separately and then try to access the pinboard then it's fine.
I see you have created a support ticket for this as well. Lets discuss on that. We should not be getting this issue..