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.
Bug 1812688 - When using IPA authentication through sssd, external users are invisible to local admin but visible to external admin accounts
Summary: When using IPA authentication through sssd, external users are invisible to l...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Users & Roles
Version: 6.7.0
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Omkar Khatavkar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-11 21:03 UTC by Pablo Hess
Modified: 2021-07-09 17:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-09 17:02:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31699 0 Normal New External users are invisible to local admin but visible to external admin accounts 2021-01-21 10:01:54 UTC

Description Pablo Hess 2020-03-11 21:03:42 UTC 
Description of problem:
This issue is present on Satellite 6.6.1 and 6.7.0-Beta. I'm filing it against 6.7.0-Beta because it's the latest version.

Satellite is set up to authenticate against an IPA server through sssd by following the steps from official docs at [1]. User group mappings are created and working fine. Now, when a remote user logs in for the first time, Satellite should create that user locally. It **kinda** does: only if you are logged in as a remote admin user will you see the new user under Administer > Users. If you are logged in as a local admin user, the remote non-admin user will not show up on the user list at Administer > Users.


Version-Release number of selected component (if applicable):
I remember seeing this issue on Satellite 6.3, possibly earlier. I just confirmed it's still happening on Satellite 6.6.1 and 6.7.0 Beta though.

How reproducible:
Every time

Steps to Reproduce:
1. Create 2 groups on an IPA server: satadmins and satusers.
2. On IPA, create user "idmadmin01" and add to satadmins.
3. On IPA, create user "idmuser02" and add to satusers.
4. Follow the steps at [1] to set up Satellite authentication against this IPA server.
5. Create 2 local groups on Satellite: satadmins and satusers, link them to their counterparts from IPA.
6. Assign all roles containing "view" or "read" to the satusers group, check the Admin checkbox for the satadmins group.
7. Open 2 separate browser sessions (use an anonymous window for the second one, or a separate account container if using Firefox).
8. On browser window 1, log into Satellite with user "idmuser02" i.e. a member of the remote satusers group.
9. On browser window 2, log into Satellite with an admin user (local or remote).
10. On browser window 2, go to Administer > Users.


Actual results:
If step #9 is done with a LOCAL admin user, idmuser02 will not appear on Satellite at step #10. In contrast:
If step #9 is done with a REMOTE admin user (idmadmin01), then idmuser02 appears on Satellite at step #10.



Expected results:
Step #10 would show all users, remote or local, regardless of you being logged into Satellite as a local or remote admin.


Additional info:

[1] Authenticating Satellite to Red Hat Identity Manager, official documentation for Satellite 6.7.0 Beta: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.7-beta/html-single/administering_red_hat_satellite/index#sect-Red_Hat_Satellite-Administering_Red_Hat_Satellite-Configuring_External_Authentication-Using_Identity_Management

Also [1] Same as the above, for Satellite 6.6: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.6/html-single/administering_red_hat_satellite/index#configuring-idm-authentication-on-satellite-server_assembly
Comment 3 Ondřej Ezr 2021-01-21 10:01:52 UTC 
Created redmine issue https://projects.theforeman.org/issues/31699 from this bug
Comment 4 Mike McCune 2021-07-09 17:02:24 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.
Note You need to log in before you can comment on or make changes to this bug.