/sso/library.js?r=###includes an sso_token that was recently destroyed. This is causing the user to get redirected to
/socialize/sso/connectwith an error page.
https://docs.oneall.com/services/implementation-guide/single-sign-on/Is there something I might be missing? Or is this an actual bug on your end?
Please sign in to your OneAll account to ask a new question or to contribute to the discussions.
Please click on the link below to connect to the forum with your OneAll account.
what have you are using as value for the lifetime of the SSO token?
I am leaving that at the default. Should it matter? I'm destroying the sso token using the rest API when I log out.
After logging out, the user is taken to our login screen. Where the situation in my original post happens.
I had unfortunately no success in reproducing the error.
What could potentially happen is that the library is included for a given r value when the user logs in, i.e.:
And that by coincidence our API generates the same value for r when the user logs out, i.e.:
The browser would then serve the library.js from it's cache and in this case it would include the old token.
We are prefixing the library.js to avoid exactly that problem.
Does the issue happen all the time or only sporadically?
It happens very sporadically.
I had to login/logout about 20 times to reproduce it once. Another time, it happened twice in a row. I think you may be correct in your assumptions though. How is that r value generated?
It seems to be fixed.
Something weird happened to my freemium account, and I am unable to reply using it. Could you mark this as answered?
I have now marked the question as answered.
Do you need help with your account?
Don't worry about it. Moving forward, this is the account I will be using. It seems the only issue is with the forums anyways.