-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Overriding typ header #530
Comments
Hello @Tilogorn ! I would love to help you support this feature, now that I know it's preventing you from using this library. The problem is, I am not sure how we can support it at this point without breaking backwards compatibility. Some potential ways to support it (just brainstorming)
I am personally leaning towards the third option. Any thoughts? |
Hi @bshaffer, I would also vote for the third option. The amount of devs who needed to change the |
THis is released in v6.10.0. Please confirm that this resolves your issue! |
@bshaffer did not forget you and will def try it out and report back. I'll have to implement new features in Q1/24 for the same project, that's a good opportunity. |
I know it has already been issued/discussed in #472 and #418 but got closed without result.
I need to change the
typ
header toJOSE
, which is sort of a pre-defined value for it, see last paragraph of this RFC 7515 chapter. The "need" is just the result of a requirement by the interface I want to talk to, which verifies that thetyp
header of my JWT equalsJOSE
. I am not in a position to argue for or against the point of it.I already use
php-jwt
on other parts of my application and love the interface and simplicity of it and I am now forced to integrate another JWT library just because you insist onJWT
hardcoded (source).Any chance you'll reconsider that decision?
The text was updated successfully, but these errors were encountered: