Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-845

Allow users to specify "group" claims for OIDC IdP configuration

    • Quality / Stability / Reliability
    • 5
    • False
    • False
    • 5
    • OCMUI Core Sprint 273, OCMUI Core Sprint 274, OCMUI Core Sprint 275

      This is the frontend story corresponding to SDA-6041. The existing UI form should be modified to include 'groups' in addition to email, name, and preferred name.

      Currently OpenID provides the following possible claims:`preferredUsername`, `name`, `email`. We need to add a new one called `groups` to the list and allow users to enter any group name that does not match the managed groups (`cluster-admins`, `dedicated-admins`).

       

      Acceptance Criteria

      • Group cannot match `cluster-admins` or `dedicated-admins`
      • UI should also validate that the cluster is 4.10 or higher before allowing the user to create OpenID IdP with group claims, as these are not supported for earlier versions of OpenShift. This is an old requirement, need to check if this is a requirement.  4.10 is EOL.
      • At least one 'group' is required. (I think, pls double-check.  All other 'Claims' fields seem to be required, but not sure about 'groups'.)  At least one claim must be entered based on the code (so either email, username, name, group). Groups are not required for the API nor should they be required for an open ID solution.

      Additional Resources

        1. openID.png
          openID.png
          113 kB
        2. new group claims.png
          new group claims.png
          68 kB
        3. new group claims-1.png
          new group claims-1.png
          69 kB
        4. clamsList.png
          clamsList.png
          69 kB

              zherman Zac Herman
              rhn-engineering-abhgupta Abhishek Gupta
              Jason Loss Jason Loss
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: