Kong JWT Signer Changelog

Changelog

2.7.x

handler.lua version: 1.9.0

• Starting with Kong Gateway 2.7.0.0, if keyring encryption is enabled, the following fields d, p, q, dp, dq, qi, and kinside jwt_signer_jwks.previous[...]. and jwt_signer_jwks.keys[...] will be marked as encrypted.

  There’s a bug in Kong Gateway that prevents keyring encryption from working on deeply nested fields, so the encrypted=true setting does not currently have any effect in this plugin.