Uploaded image for project: 'RHOS Request for Features'
  1. RHOS Request for Features
  2. RHOSRFE-166

Support EntraID with OIDC to keystone

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • False
    • False
    • Hide

      None

      Show
      None

      Feature Request Overview (mandatory - Complete while in New status){_}
      {}What user goal or problem do you need to solve?{_} 

      We had several requests to support EntraID (formerly Azure AD) through OICD back to keystone. At the moment, the configuration requires a support exception.

      Business justification (mandatory - Complete while in New status)
      How would this feature benefit the customer?

      Customers with EntraID are fully supported when using it as data source to keystone.

      Functional requirements (mandatory - Complete while in New status){_}
      {}What do you want the result of this feature to be? Add as many requirements as needed.{_}

      • EntraID is a supported OIDC back end, on par with Red Hat build of Keycloak.
      •  

      Describe the customer impact

      IMPORTANT: Do not include customer names.

      • Provide links to the account project
      • Provide links to any related support tickets (open or closed)

      For details on connecting Jira issues to an account, see Connecting Jira Issues to Accounts.

      (Optional) Point of contact

      • Provide any additional points of contact for this feature request, such as an account executive, SA, or TAM: 
      •  

      (Optional) Additional links

      Click More > Link to add any links to issues, such as an outcome, that are related to this feature request.

              Unassigned Unassigned
              jjung@redhat.com JP Jung
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: