I’m using the rest API, so for a user logout, I need to supply a token in the header however, lets assume my application has crashed and im no longer caching the token. I can’t logout the user, and I can’t log in because I’m already logged in. Am I missing something?
Thanks for the answer Mark. I can save the token on the client side, however I need to understand what would happen in a scenario where the token is lost (lets just say catastrophic failure of the client user device) and we only allow one login. It seems the user is then stuck in a permanently logged in state? I tried adjusting the setting for “session timeout”, but that didn’t seem to have an affect.
[reply user_id=123][h4]Jim Cramer wrote:[/h4]Thanks for the answer Mark. I can save the token on the client side, however I need to understand what would happen in a scenario where the token is lost (lets just say catastrophic failure of the client user device) and we only allow one login. It seems the user is then stuck in a permanently logged in state? I tried adjusting the setting for “session timeout”, but that didn’t seem to have an affect.[/reply]The value for session timeout might only apply to sessions created after it was set? (existing sessions may not be updated)
Hi Jim,
Is the local storage on the client side an option to save the user-token value? If not, please clarify why.
You can login the user if you enable the “Multiple Logins” option in the console (see the Users > Login screen).
Regards,
Mark