-
Epic
-
Resolution: Won't Do
-
Major
-
None
-
2.5 GA
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
The request comes from the following use case:
A JWT token can be issued by two different OIDC providers:
- provider1.com
- provider2.com
When a client application calls the Service it is not possible to determine by which OIDC Provider the tokens have been issued. The request is to have the ability to configure 2 OIDC providers in a service.
Currently it is only possible to use a single OIDC Provider that is validated in the integration page of the service with the OpenID Connect Issuer.
Additionally, the same request for enhancement is needed for the introspection policy. Currently it is only possible to validate the token against the OIDC provider defined in the OpenID Connect issuer.