Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-2546

Ability to use multiple OIDC providers with a single service

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 2.5 GA
    • Gateway, System, Zync
    • None
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • 0
    • 0% 0%

      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.

            Unassigned Unassigned
            rhn-support-avilatus Anna Vila Tusell
            Votes:
            4 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: