Individual JWT Secrets - Key not authorized:signature is invalid

[Paulo_Renato]

@leon

When you specify secret in KID, Tyk do not really support automatically decoding base64 secrets. So you need to specify the ‘real’ secret used to sign the token. E.g. you should not base64 encode secret, for using it in Tyk.

From docs:

"enable_jwt": true,
"jwt_source": "BASE64-Encoded secret",
...

and:

"jwt_data": {
  "secret": "Secret"
}

@leon

Does it makes sense?

Doesn’t in the sense the docs are not clear, and not consistent

All libraries I have worked until now for validating JWT’s support by default Base64 encoded secrets, thus I am curious to know the reason why TYK is supporting them in on part of the configuration and not in the other?

Thanks for your help