Open SiluniPathirana opened 3 months ago
In APIM 4.2.0, Even after configuring the following configuration in the deployment.toml file.
[apim.jwt] enable = true encoding = "base64url" # base64,base64url
We still could observe the base64 encoded value in the backend JWT not base64url encoded value
{ "typ": "JWT", "alg": "RS256", "x5t": "ODE3Y2ZhMTBjMDM4ZTBmMjAyYzliYTI2YjRhYTZlOGIyZmUxNWE3YQ==", "kid": "Q049bG9jYWxob3N0LCBPVT1XU08yLCBPPVdTTzIsIEw9TW91bnRhaW4gVmlldywgU1Q9Q0EsIEM9VVMjMTY3NzA4OTI4Mw" }
Thanks, Siluni
N/A
APIM
4.2.0
No response
Description
In APIM 4.2.0, Even after configuring the following configuration in the deployment.toml file.
[apim.jwt] enable = true encoding = "base64url" # base64,base64url
We still could observe the base64 encoded value in the backend JWT not base64url encoded value
{ "typ": "JWT", "alg": "RS256", "x5t": "ODE3Y2ZhMTBjMDM4ZTBmMjAyYzliYTI2YjRhYTZlOGIyZmUxNWE3YQ==", "kid": "Q049bG9jYWxob3N0LCBPVT1XU08yLCBPPVdTTzIsIEw9TW91bnRhaW4gVmlldywgU1Q9Q0EsIEM9VVMjMTY3NzA4OTI4Mw" }
Thanks, Siluni
Steps to Reproduce
N/A
Affected Component
APIM
Version
4.2.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response