Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is it a hybrid authentication system? #527

Closed
d3crypt3d opened this issue Feb 6, 2016 · 2 comments
Closed

Is it a hybrid authentication system? #527

d3crypt3d opened this issue Feb 6, 2016 · 2 comments

Comments

@d3crypt3d
Copy link

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.

@rdupz
Copy link

rdupz commented Feb 20, 2016

+1

@lynndylanhurley
Copy link
Owner

I think Omniauth is the only part of this system that uses session storage.

In this chain of events:

Client -> Rails API -> Provider Auth -> Rails API -> Client

Session storage is used when going from the Rails API to the Provider and back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants