You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
As I know, token-based authentication system assumes stateless server-side, which means no session is persisted. But I discovered it still uses sessions under the hood. Seems because it is build on the top of Devise, which, in turn, uses Warden's functionality. If it's true, which piece of information is stored in a session variable and which one in the token (in comparison with traditional Device)?
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Hello.
As I know, token-based authentication system assumes stateless server-side, which means no session is persisted. But I discovered it still uses sessions under the hood. Seems because it is build on the top of Devise, which, in turn, uses Warden's functionality. If it's true, which piece of information is stored in a session variable and which one in the token (in comparison with traditional Device)?
Thanks in advance.
The text was updated successfully, but these errors were encountered: