Bug 1417134

Summary: Usergroup Sync Using Wrong Base DN
Product: Red Hat Satellite Reporter: Satellite Program <pm-sat>
Component: Users & RolesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Ivan Necas <inecas>
Severity: low Docs Contact:
Priority: medium    
Version: 6.2.2CC: adam.killeen, bbuckingham, dhlavacd, dlobatog, ehelms, inecas, jcallaha, mhulan, zhunting
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1387383 Environment:
Last Closed: 2018-02-21 16:51:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1387383    
Bug Blocks:    

Comment 2 Ivan Necas 2017-08-30 09:05:52 UTC 
Verification version: Satellite 6.3 Snap 13

Verification steps:

1. enable ldap debug level logging in /etc/foreman/settings.yaml

:loggers:
  :ldap:
    :enabled: true
    :level: debug

2. configure POSIX ldap authentication, set group_base_dn to base=ou=groups,dc=example,dc=com 

3. log in as the ldap user, watching the logs about what base was used:

2017-08-30 05:00:42 a5fa6925 [ldap] [D]   op bind (10.8ms)  [ result=success ]
2017-08-30 05:00:42 a5fa6925 [ldap] [D]   authenticate (39.9ms)  [ user=test1 ]
2017-08-30 05:00:42 a5fa6925 [ldap] [D]   op bind (11.1ms)  [ result=success ]
2017-08-30 05:00:42 a5fa6925 [ldap] [D]   op search (16.8ms)  [ filter=, base= ]
2017-08-30 05:00:42 a5fa6925 [ldap] [D]   op search (15.1ms)  [ filter=(memberuid=test1), base=ou=groups,dc=example,dc=com ]
2017-08-30 05:00:42 a5fa6925 [ldap] [D]   group_list (45.2ms)  [ user=test1 ]
Comment 3 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