Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Hi
I like to create a user account with only READ rights on the Satellite Server. That means, a user which is able to read all system/channel/entitlement etc. information but is not able to change any of these items. At the moment I only see following Roles
Monitoring Administrator
Activation Key Administrator
Configuration Administrator
Channel Administrator
Organization Administrator
System Group Administrator
It seems that none of them is satisfactory
Regards Mathias
This event sent from IssueTracker by tdunnon [SEG - Feature Request]
issue 117658
Satellite 6 ships with a 'readonly' role that can be assigned to new users. This allows them to login, look but not change anything in the system.
This protects objects at the API/CLI and WebUI levels to ensure no write access is granted.
Moving to ON_QA so QE can state if they have verified that 'readonly' user works.