-
Notifications
You must be signed in to change notification settings - Fork 434
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
Complex keys in the "keys_to_sign" property #852
Comments
Hello @ridgarou , this functionality is not currently supported |
Thanks for the response. I understand that this functionality is not currently available. I would like to know if it would be possible to implement it in the future. I think this would be very useful for users who need to sign tokens with more complex object structures. |
I will leave this issue open for a while so people can upvote the functionality with a 👍 . It is the first time I've seen this requirement in six years, so I don't think it is very common among KrakenD users, but let's see what the community says |
Version of KrakenD you are using
v2.5.0
Description
I have a backend service that, upon login, returns the access_token in a nested object and I would like to sign it with the JWT signing functionality.
Problem
The JWT signing functionality only allows you to specify properties to sign in keys_to_sign that are at the root of the main object. In this case, the access_token property is nested within the user object.
Is there a way to sign the user.access_token property with the JWT signing functionality?
The text was updated successfully, but these errors were encountered: