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.
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.
Created redmine issue http://projects.theforeman.org/issues/6372 from this bug
Upstream bug assigned to tcaspy
Upstream bug component is Multi Org
*** Bug 1246670 has been marked as a duplicate of this bug. ***
*** Bug 1280303 has been marked as a duplicate of this bug. ***
Upstream bug assigned to dlobatog
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/6372 has been resolved.
Do we have any ETA for when this will land in Satellite?
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
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.
*** Bug 1397185 has been marked as a duplicate of this bug. ***
*** Bug 1337861 has been marked as a duplicate of this bug. ***