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 1394352 - Users authenticated via external ldap contain no default context/location
Summary: Users authenticated via external ldap contain no default context/location
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Organizations and Locations
Version: 6.0.3
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: Unspecified
Assignee: Daniel Lobato Garcia
QA Contact: Kedar Bidarkar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On: 1104822
Blocks: 1353215 GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker 1287901
TreeView+ depends on / blocked
 
Reported: 2016-11-11 19:25 UTC by Bryan Kearney
Modified: 2021-09-09 11:59 UTC (History)
22 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1104822
Environment:
Last Closed: 2018-02-21 16:51:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 6372 0 None None None 2016-11-11 19:26:02 UTC
Red Hat Knowledge Base (Solution) 1460183 0 None None None 2016-11-11 19:26:02 UTC

Comment 2 Bryan Kearney 2016-11-11 21:19:24 UTC
Upstream bug assigned to dlobatog

Comment 3 Bryan Kearney 2016-11-11 21:19:30 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/6372 has been resolved.

Comment 8 Kedar Bidarkar 2017-08-18 10:25:22 UTC
This bug is verified with Sat6.3.0 satellite-6.3.0-snap11.0

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 was 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.

----

Comment 9 Satellite Program 2018-02-21 16:51:07 UTC
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/RHSA-2018:0336


Note You need to log in before you can comment on or make changes to this bug.