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

[OCM UI] A user granted with only role "machine pool editor", allowed to make other actions on the cluster

    • Icon: Story Story
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • Core UI
    • 1
    • False
    • HAC Console Sprint 244, OCM UI Sprint 244b, OCM UI Sprint 245, OCM UI Sprint 246, OCM UI Sprint 247, OCM UI Core Sprint 248, OCM Core Sprint 249, OCM Core Sprint 250, OCM Core Sprint 251, OCM Core Sprint 252, OCM Core Sprint 253, OCMUI Core Sprint 254, OCMUI Core Sprint 255, OCMUI Core Sprint 256, OCMUI Core Sprint 257, OCMUI Core Sprint 258, OCMUI Core Sprint 259, OCMUI Core Sprint 260, OCMUI Core Sprint 261, OCMUI Core Sprint 262, OCMUI Core Sprint 263, OCMUI Core Sprint 264, OCMUI Core Sprint 265

      Description of problem:

      An org member user has granted with role permission "machine pool editor" for a cluster. But in org member user login session, the UI options under settings tabs are enabled and user allowed to schedule the updates for the same cluster. It is wrong and we should restrict the user only machine pool related action for this role from UI.

      How reproducible:

       Always

      Steps to reproduce:

      1. Launch OCM UI staging and login as org-admin user.
      2. Open a ROSA hypershift cluster.
      3. Go to access control tab > OCM roles and access , click "Grant" button.
      4. Input Redhat login with a valid user name (ex: use a org-member user)
      5. Select Role as Machine pool editor and Click on "Grant role".
      6. Login to OCM UI Staging with the user granted permission in step 4 .
      7. Select and Open  the cluster(same as step 2).
      8. Go to "Settings" tab  and see the update strategy options. 
      9. Try to schedule the update and see the behavior.

      Actual results:

      The user allowed to schedule cluster update from settings tab wrongly when the user has  granted with the role "machine pool editor". 

      Expected results:
      The user should not be allowed to schedule cluster update from settings tab and  the role "machine pool editor" should have access related to machine pool requirements.

              rh-ee-egilman Liza Gilman
              jmekkatt@redhat.com Jayakrishnan Mekkattillam
              Jayakrishnan Mekkattillam Jayakrishnan Mekkattillam
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: