Bug 2257333

Summary:	Improve the error message when listing/viewing capsules via API w/o permissions
Product:	Red Hat Satellite	Reporter:	Vladimír Sedmík <vsedmik>
Component:	Capsule - Content	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.15.0	CC:	iballou, rlavi
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:40:29 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 Vladimír Sedmík 2024-01-08 20:47:36 UTC

Description of problem:
Sequel of BZ#2096930 to improve the error message.
Non-admin user needs the `view_smart_proxies` permission to list/view smart proxies via API, but he is advised he needs `manage_capsule_content` instead.


Version-Release number of selected component (if applicable):
6.15.0


How reproducible:
always


Steps to Reproduce:
1. Try to list/show an external capsule via API for a user with no permissions.


Actual results:
$ curl -k -u unauth:unauth https://satellite.redhat.com/katello/api/capsules/2
{
  "error": {"message":"Access denied","details":"Missing one of the required permissions: manage_capsule_content","missing_permissions":["manage_capsule_content"]}
}


Expected results:
$ curl -k -u unauth:unauth https://satellite.redhat.com/katello/api/capsules/2
{
  "error": {"message":"Access denied","details":"Missing one of the required permissions: view_smart_proxies","missing_permissions":["view_smart_proxies"]}
}

Comment 3 Eric Helms 2024-06-06 16:40:29 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.