Bug 2247498

Summary:	User without necessary permissions can go to /job_invocations/new and see a somewhat broken page due to lacking permissions
Product:	Red Hat Satellite	Reporter:	Adam Ruzicka <aruzicka>
Component:	Remote Execution	Assignee:	kmalyjur
Status:	CLOSED MIGRATED	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.13.0	CC:	aruzicka, rlavi
Target Milestone:	stream	Keywords:	MigratedToJIRA, Triaged, UserExperience
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-foreman_remote_execution-12.0.3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:31:53 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 Adam Ruzicka 2023-11-01 15:51:48 UTC

Description of problem:
User without necessary permissions can go to /job_invocations/new and see a somewhat broken page due to lacking permissions. Some fields fail to load, 

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

How reproducible:
always


Steps to Reproduce:
0. Have a user without any permissions
1. Go to https://$sat_fqdn/job_invocations/new


Actual results:
The job wizard loads, but shows various 403 errors all over the place.


Expected results:
There is an error page listing all the permission that the user is missing to be able to sensibly use the page.


Additional info:
Forked off from https://bugzilla.redhat.com/show_bug.cgi?id=2214285

Comment 1 Eric Helms 2024-06-06 16:31:53 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.