I have a user with the following permissions: <pre> shell# hammer --output json user info --login XXXX { "Id": XXXX, "Login": "XXXXX", "Name": "XXXXXXXXXXXXXXXX", "Email": "XXXXXXXXXXXXXXXXX", "Admin": false, "Authorized by": { "id": 1, "type": "AuthSourceInternal", "name": "Internal" }, "Locale": "XX", "Timezone": "XX", "Last login": "XXXXXXXXXXXXX", "Default organization": null, "Default location": null, "Roles": [ { "name": "AccountAdministrator", "id": 9 }, { "name": "Anonymous", "id": 8 } ], "User groups": [ ], "Created at": "XXXX", "Updated at": "XXXX" } shell# hammer --output json filter list --search "--role=AccountAdministrator" { "Id": XXXX, "Resource type": "SmartProxy", "Search": "none", "Unlimited?": true, "Role": { "name": "AccountAdministrator", "id": XXXX }, "Permissions": [ "view_smart_proxies", "view_smart_proxies_autosign", "view_smart_proxies_puppetca", "edit_smart_proxies_puppetca", "destroy_smart_proxies_puppetca" ] }, </pre> However on centos7 + foreman-1.11.0-1.el7.noarch I can not see the certificates (See Screeshot) If I grant "Manager" permissions to the user, it still does not work.
Created from redmine issue http://projects.theforeman.org/issues/14505
Upstream bug assigned to tbrisker
Non admin users which have proper permissions can not see link to smart proxy detail page from smart proxy index. Also, clicking on buttons to certificates or autosign leads to the details page but both tabs are not shown.
*** Bug 1324511 has been marked as a duplicate of this bug. ***
Moving to POST since upstream bug http://projects.theforeman.org/issues/14505 has been closed ------------- Anonymous Applied in changeset commit:a88d4a3e9790bf863634688b286ec6f9eed12907.
Verified in Satellite 6.2 Beta Snap 13. Users with permissions as low as viewer can now see the details of smart proxies.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1501