-
-
Notifications
You must be signed in to change notification settings - Fork 240
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
Use sub claim instead of identity for interoperatibility #65
Comments
psafont
added a commit
to psafont/flask-jwt-extended
that referenced
this issue
Jul 12, 2017
Related to issue vimalloc#65
psafont
added a commit
to psafont/flask-jwt-extended
that referenced
this issue
Jul 12, 2017
Related to issue vimalloc#65
psafont
added a commit
to psafont/flask-jwt-extended
that referenced
this issue
Jul 12, 2017
Related to issue vimalloc#65
Got this merged. Pypi changed how packages are uploaded out from under me, so I need to figure that out later tonight, then I'll get it setup there. Cheers. |
Released in 3.1.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
The library uses the claim
identity
for identifying the subject. This makes the library a bit awkard to interop with external identity providers or client implementations.The JWT RFC recommends using
sub
for identifying the principal:I was thinking about making the "identity" claim to be changeable with a config key. This would allow for several pro:
As for the cons, while decoding should be easy to change, encoding is another matter.
Thoughts?
The text was updated successfully, but these errors were encountered: