Complex keys in the "keys_to_sign" property

[ridgarou]

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.

{
  "user": {
    "access_token": {
                "aud": [ "xxxxxxxxxxxxxxxxxxxxxx" ],
                "exp": 1709545713,
                "iat": 1709542113,
                "jti": "e1436772-d038-4488-8870-127d35833c1c",
                "nbf": 1709542113,
                "scope": "xxxxxxxxxxxxxxxxxxxxxx-yyyyyyyy",
                "sub": "6a792e214a3ca1e4b1d90d6b301c8babc89415cc",
            },
            "expires_at": 1709545713655
  }
}

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?

[alombarte]

Hello @ridgarou , this functionality is not currently supported

[ridgarou]

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.

[alombarte]

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