Olivia Wenzel - I am on the same team as @Ashut...
I am on the same team as @Ashutosh Patil 🙂 To provide some more detail about what we're experiencing - We're embedding Spotter in our platform and it times out after about 5 minutes of active use. It's not a query timing out - we send some chats, maybe hit reset, and about 5 minutes in, it times out. There appears to be a keep alive message that keeps going out to thoughtspot:
curl 'https://restoreskills.thoughtspot.cloud/callosum/v1/session/isactive' \
-H 'accept: /' \
-H 'accept-language: en-US,en;q=0.9' \
-H 'authorization: Bearer JHNoaXJvMSRTSEEtMjU2JDUwMDAwMCRzZHlVRGlvRTVBcldrK1NpWjVGZGtnPT0kWVRCdlRQS3pPTTBuME96eTRuZk1nNXQxSjFvUzBMVGpkWXVUUzVCbk82cz0' \
-b 'JSESSIONID=b1cd1ceb-21a2-4252-aa3f-a1fbcfe11997; clientId=ba8654fb-621d-4454-8bb2-962076360245' \
-H 'priority: u=1, i' \
-H 'referer: https://restoreskills.thoughtspot.cloud/v2/?embedApp=true&hostAppUrl=orthocare-enterprise.stage-insights.restoreskills.com&viewPortHeight=958&viewPortWidth=885&sdkVersion=1.39.2&authType=AuthServerCookieless&blockNonEmbedFullAppAccess=true&cookieless=true&disableAction=[%22pin%22,%22save%22,%22edit%22,%22previewDataSpotter%22]&hideAction=[%22reportError%22]&iconSprite=cdn.jsdelivr.net/gh/restore-skills/spotter-icon/assets/image2vector.svg&preAuthCache=true&overrideConsoleLogs=true&clientLogLevel=DEBUG&isSpotterExperienceEnabled=true&disableSourceSelection=true&hideSourceSelection=true' \
-H 'sec-ch-ua: "Google Chrome";v="137", "Chromium";v="137", "Not/A)Brand";v="24"' \
-H 'sec-ch-ua-mobile: ?0' \
-H 'sec-ch-ua-platform: "macOS"' \
-H 'sec-fetch-dest: empty' \
-H 'sec-fetch-mode: cors' \
-H 'sec-fetch-site: same-origin' \
-H 'sec-fetch-storage-access: active' \
-H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36' \
-H 'x-session-check: true'
The message appears to switch from 200 to 401 after 5 min for no clear reason.
7 Replies
I see you are using cookieless. The token in cookieless expires after 5 mins. Can you set autologin to true to make sure ti logs you back in. cc @Justin
Hey @shikharTS
We tried with added this flag in "init" method
but it is not resolving the issue
This APIis getting hit after specific time interval : https://restoreskills.thoughtspot.cloud/callosum/v1/session/isactive , and we are receiving 401 from it
Hey @Ashutosh Patil - The isActive call will fail but we have one authExpiry Event that will be caught and we autoTrigger token fetch automatically again. ( for cookieless even without the flag )
Is it showing not logged in after 5 mins or say failing further calls?
Or is your concern about just the failed call of isActive?
Because after refetching token automatically in UI you won't see any problem or inconsistency.
Thanks
Hey @yuichirio_ha , i have updated " authType: AuthType.TrustedAuthToken," in init merhod and it get resolved.
Let us investigate internally if autologin for TrustedAuthTokenCookieless is broken. It should not be, and we recommend using cookieless instead of TrustedAuthToken, to support future cases when browsers start blocking third party cookie. Will comment back here
Did anything come of this? I am experiencing the same issue where using
TrustedAuthTokenCookieless results in a pattern where the inactive calls fails with a 401 then the autoLogin gets a new token
yes this is correct. inactive calls fail with a 401 to then the autologin gets a new token. Getting a token is reactive, rather than proactive..