-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
Support OAuth2 with JSON Web Token #211
Comments
Is this fork safe to merge into the mainline? I'm interested in using this for Apple SSO |
Just to note, I think this implements §2.2 of RFC 7523, but not §2.1 (which requires a new grant type). |
I will do what I can by forking and modifying it on my own to support that section... trying to avoid handrolling an oauth2 implementation if possible for Apple's SSO! |
Apple's SSO seemed to only require a dynamic client_secret, as described in their docs here. I've essentially just added a step before requesting an access token in my own codebase that generates this JWT using jwt-simple, then overwrite the client secret with that value. |
JWTs add significant complexity that I would like to avoid in this crate. See earlier comment. Just as I implemented OpenID Connect in a separate crate on top of this one, I think RFC 7523 is complex enough to merit its own crate (maintained by someone else). If there are API changes needed to this crate in order to be able to build that separate crate (e.g., stuff like |
For me it works fine setting the |
Don't we support urn:ietf:params:oauth:grant-type:jwt-bearer in getting an access token?
The text was updated successfully, but these errors were encountered: