Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2106270

Summary: [RFE][GSS][RHSSO user should get role assigned automatically after enabling single-sign-on in ceph dashboard]
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: vadeshpa
Component: Ceph-DashboardAssignee: Afreen <afrahman>
Status: CLOSED DEFERRED QA Contact: Sunil Angadi <sangadi>
Severity: medium Docs Contact:
Priority: high    
Version: 5.0CC: afrahman, assingh, ceph-eng-bugs, cephqe-warriors, epuertat, ksachdev, nia, saraut
Target Milestone: ---Keywords: FutureFeature
Target Release: 9.1   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-08-28 10:18:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description vadeshpa 2022-07-12 09:10:20 UTC 
Description of problem:
The customer wants the RHSSO user of a particular group will get the role assigned automatically after enabling the RHSSO user to ceph dashboard without adding the role manually to the user.



Version-Release number of selected component (if applicable):
RHCS 5.x



Additional info:
we can assign the role at the user level as mentioned in the dashboard guide but the customer wants to assign the role at the group level so when we assign the role to the group the users in the group will get the role assigned automatically without adding it manually
Comment 25 Sahina Bose 2025-08-28 10:18:57 UTC 
Closing this bug as part of bulk closing of bugs that have been open for more than 2 years without any significant updates for the last 3 months. Please reopen with justification if you think this bug is still relevant and needs to be addressed in an upcoming release