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.
DescriptionJan Pazdziora (Red Hat)
2014-05-07 11:57:55 UTC
Description of problem:
Today, the last commit for the external authentication support (http://projects.theforeman.org/issues/5031) was merged to Foreman develop. Since it won't be in Foreman 1.5.0, we'd need it cherry picked for Satellite 6.0.
The commit is 1e8a50848d3636241f12ae584183ba19934cd120 since I believe all previous commits for the feature are in Foreman 1.5 (that seems to have been branched at 936bab04d3b1d3136c28b77129cc052bcd04260c.
Version-Release number of selected component (if applicable):
Satellite 6.
How reproducible:
Deterministic.
Steps to Reproduce:
1. Attempt to use the product with external authentication against Identity Management / FreeIPA.
2. Have LookupUserGroupsIter REMOTE_USER_GROUP enabled and external group mapping defined, verify that groups are populated.
3. Change group memberships or one of the name/email attributes of existing Foreman user in IdM.
4. Log in as that user to Foreman.
Actual results:
Without the commit merged, attributes / group membership will not be up-to-date.
Expected results:
With the change in, attributes / group membership will be up-to-date.
Additional info:
Comment 1Jan Pazdziora (Red Hat)
2014-05-07 12:03:47 UTC
This is related to bug 1084136. Not sure if they should block each other and in what direction, so just mentioning it here.
Set up the product with external authentication against Identity Management / FreeIPA, created usergroup and user in IPA, and usergroup with linked external usergroup in Sat 6.
I assigned user to usergroup in ipa.
On first successfull login, user has been registered to the relevant Sat 6 usergroup based on the link with external IPA usergroup.
I removed usergroup from user.
On the second login, the usergroup has been removed.