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.
Upon login using an 'external' user. The user cannot do anything. I've even attempted to specify an external group, but there is no context/location settings in the external group settings.
Comment 1RHEL Program Management
2014-06-04 18:54:16 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
This bug is verified with Sat6.2.5 satellite-6.2.5-1.0.el7sat.noarch
Now upon trying to create a LDAP auth source, for the ldap auth source we need to specify the taxonomies ( i.e, ORG and LOC ).
After, configuring external user-groups and upon the user trying to login to sat6, the user was able to inherit the ORG and LOC from the set values of LDAP auth source.
----
Some detailed explanation from the commit which fixes this issue,
In an installation that uses taxonomies, when an user logs in for
the first time and gets its account created via LDAP, it has no
taxonomies.
This is a problem, as even if the user has all the roles it needs from
external user groups, an admin needs to manually set the taxonomies for
every new user.
This commit fixes that by assigning the taxonomies from the LDAP auth
source to the user when it logs in for the first time. It does not
update them on every login, as after the user has logged in, user
taxonomies are left to the Foreman administrator to manage.
----
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:2940