Can't use - Dedicated Private Key for Signing JWT

Products

• CA API Gateway

Issue/Introduction

We are trying to use - Dedicated Private Key for Signing JWT
As defined here : 
https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-management-oauth-toolkit/4-2/openid-connect-implementation/use-a-dedicated-private-key-for-signing-jwt.html

But when we create Tokens it still using the default_ssl_key as a signing key instead of our dedicated key.

 

Environment

Release : 10.1

Component : API GATEWAY

Cause

Doc bug - sent info to doc tech team 

Resolution

Follow the steps from the docs 

https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-ma[…]mentation/use-a-dedicated-private-key-for-signing-jwt.html

For "Configure the Key ID"

Customers need to copy TWO context variables from OTK id_token KID Configuration  to  #OTK id_token KID Configuration 

You also need to copy the KID_HEADER  context variable

Results: 

{

  "typ": "JWT",

  "alg": "RS256",

  "kid": "jwk-key"

}