-
Notifications
You must be signed in to change notification settings - Fork 453
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
Add "typ" attribute in JWT header when signing tokens #711
Comments
Hi @MinKyawNyunt , this feature is not currently supported, but we can add it in future releases |
for future references, the change should go here: https://github.com/krakendio/krakend-jose/blob/master/jws.go#L141 |
This issue is easy for contributing. Everyone can work on this.
|
Hello @kpacha @alombarte Can I work on this ? |
@AlyHKafoury sure! contributions are always welcome!!! |
would this be enough ? krakend/krakend-jose#119 , or there is other places where the header will need to be modified. |
Thank you very much @AlyHKafoury for your contribution! I see there are minor changes requested in the PR, if you add them we will release this in KrakenD 2.5 which is round the corner |
I will work on it now and see if I can get a clear |
This will be released with v2.6, planned on mid Feb 2024 |
Is there any connected issues that are urgent I can contribute to ?
…________________________________
From: Daniel López ***@***.***>
Sent: Tuesday, January 16, 2024 3:04 PM
To: krakend/krakend-ce ***@***.***>
Cc: Aly Kafoury ***@***.***>; Mention ***@***.***>
Subject: Re: [krakend/krakend-ce] Add "typ" attribute in JWT header when signing tokens (Issue #711)
This will be released with v2.6, planned on mid Feb 2024
—
Reply to this email directly, view it on GitHub<#711 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIKUBD2JA4SIG5BTDDUPLX3YOZ3GVAVCNFSM6AAAAAAXDIRCPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJTG4YDKOBUGY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi @AlyHKafoury , thank you for your support! There are no urgent issues, but feel free to navigate through the almost 1000 questions and requests we opened have: https://github.com/search?l=&o=asc&q=user%3Akrakend&state=open&type=Issues |
Environment info:
Describe what are you trying to do:
Adding additional in Header
configuration:
jwt decode header output
expected decode header result
The text was updated successfully, but these errors were encountered: