Add the ability to override the client ID which is used as the
audience of the JWToken. Currently, the client ID obtained through the X-Dataporten-Clientid header is always used. In order to make it easier to associated JWTokens with specific Kubernetes clusters, we want to make it possible to always use a specific client ID as the audience.
Please register or sign in to comment