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

3scale SSO integrations allowing multiple integrations of the same Id Provider

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Minor Minor
    • None
    • 2.10 GA
    • System
    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Undefined
    • Hide

      Navigate to Account Settings > Users > SSO Integrations and click on New SSO Integration and add as many new integrations as you want.

      Show
      Navigate to  Account Settings > Users > SSO Integrations  and click on  New SSO Integration  and add as many new integrations as you want.

      Following the documentation RH-SSO or Auth0 member authentication. When navigating to Account Settings > Users > SSO Integrations, and clicking on New SSO Integration it is possible to add and publish more than one integration to the same SSO Provider. This behavior is bringing us a problem because when you go to the 3scale Admin Portal login page there will be a list of SSO login options, it's not allowed to rename these integrations, and the user will not be able to identify on which option belongs to his Id Provider.

      I brought this subject to the Product team and they said that this is not expected to happen and it must be a bug because the system should not allow (and there's no use case for this behavior at the moment). It is possible to publish/activate two or more integrations for the same type of IdP so they appear with the same name in the login form.

      3scale should prevent the user from publishing more than one integration for the same type of IdP. 

        1. image (1).png
          25 kB
          Gustavo Pereira
        2. image (2).png
          71 kB
          Gustavo Pereira

              Unassigned Unassigned
              gpereira@redhat.com Gustavo Pereira
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: