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
{{ message }}
This repository has been archived by the owner on May 24, 2023. It is now read-only.
Currently on successful validation token is always saved to ctx.Locals(), but I'm not sure it's necessary, as if we can always get this information from the ctx anyway, either headers, or cookies or URL params. What might be valuable is to have claims saved instead.
And in any case, we should not decide, but rather give a developer an option on how to treat this situation – the best would be to update the signature of SuccessHandler and pass a JWT there. And in case if a developer need it – he / she could save information that they need where they want. While today it's even impossible to switch off this behavior.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently on successful validation token is always saved to
ctx.Locals()
, but I'm not sure it's necessary, as if we can always get this information from thectx
anyway, either headers, or cookies or URL params. What might be valuable is to have claims saved instead.And in any case, we should not decide, but rather give a developer an option on how to treat this situation – the best would be to update the signature of
SuccessHandler
and pass aJWT
there. And in case if a developer need it – he / she could save information that they need where they want. While today it's even impossible to switch off this behavior.The text was updated successfully, but these errors were encountered: