-
-
Notifications
You must be signed in to change notification settings - Fork 58
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 asymmetric algorithms #40
Support asymmetric algorithms #40
Conversation
For asymetric algorithms, the decoding secret is different than the encoding secret. This change adds support for an optional decoding secret configuration.
Reason for PR: I would love to be able to use this library with RS256 algorithm, which necessitates this change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Thanks for your collaboration. Do you need a new release with this change?
My pleasure 🙂
sure, that would be awesome! |
Released in v0.7.0! 🚀 |
I just upgrade to 0.7.0 today and find it maybe having a break change, I'm not yet check it, but I'm sure in client code side, it must do some configuration. |
Please, report if you find more details. Thanks! |
I also encountered a breaking change with this here -- is there some configuration change we need to make in order to be compatible with the change introduced in this PR? Effectively, the JWT strategy no longer works in our case. I can dig in more later, but am happy to introduce an update / config change if there's a suggested one to comply with this new feature. |
Please, see waiting-for-dev/devise-jwt#250 |
Description
For asymmetric algorithms, the decoding secret is different than the encoding secret. This change adds support for an optional decoding secret configuration.