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
I am working on a rails/jwt integration (sirwolfgang/jwt_keeper), which I would like to integrate with sorcery.
One of the key things is that the tokens are not stored in sessions, but are handled by the frontend and stored in local storage. (Depending on how you use them) I bring this up because currently sorcery default auths by the login_from_session then by login_from_other_sources. I think it would be favorable to make this slightly more modular by not having a session based default, but rather have login_from_sessions be one of the (priority loaded) methods. This would allow pretty seamless integration with completely other flows like JWT(which could use a few different approaches as well).
The text was updated successfully, but these errors were encountered:
I am working on a rails/jwt integration (sirwolfgang/jwt_keeper), which I would like to integrate with sorcery.
One of the key things is that the tokens are not stored in sessions, but are handled by the frontend and stored in local storage. (Depending on how you use them) I bring this up because currently sorcery default auths by the
login_from_session
then bylogin_from_other_sources
. I think it would be favorable to make this slightly more modular by not having a session based default, but rather havelogin_from_sessions
be one of the (priority loaded) methods. This would allow pretty seamless integration with completely other flows like JWT(which could use a few different approaches as well).The text was updated successfully, but these errors were encountered: