-
-
Notifications
You must be signed in to change notification settings - Fork 243
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 for AES256GCM encryption/decryption? #154
Comments
AES (or really any encryption) is part of jwe, which we do not support yet. I though about it at the beginning but I did not need it and so far it looked like neither did anyone else using this. I'll take a look later as to how hard it would be to implement this. |
Thanks for looking into this. The application actually uses encryption and
signing of the JSON tokens (first generating a signed token and then
encrypting that blob) for passing user authentication information around.
Your library works well for signing the tokens, but the application this is
being used in, needs to decrypt tokens received from a different
application.
Thanks,
Noel Otterness
…On Wed, Aug 11, 2021 at 11:22 AM Dominik Thalhammer < ***@***.***> wrote:
AES (or really any encryption) is part of jwe, which we do not support
yet. I though about it at the beginning but I did not need it and so far it
looked like neither did anyone else using this. I'll take a look later as
to how hard it would be to implement this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#154 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASLHAWBAKC4V3SN5MNETEE3T4KWV7ANCNFSM5B7A4XQQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>
.
|
Hi everybody! Is there any update on that front? Thanks in advance |
No but if you need it feel free to contribute :) IF you have ideas how'd you implement let us know and we can make sure you are on the right track :) |
Looking through the code I could not find support for AES256GCM encryption (for the CJOSE C library it is referred to using: "alg"
is CJOSE_HDR_ALG_DIR and "enc" is set to CJOSE_HDR_ENC_A256GCM).
Is there support for this in jwt-cpp and if so, how would I go about using it to encrypt/decrypt a signed token?
Thanks
The text was updated successfully, but these errors were encountered: