Bug 1882535

Summary: The user group feature is not working as expected with openldap "user_list method"
Product: Red Hat Satellite Reporter: Waldirio M Pinheiro <wpinheir>
Component: LDAPAssignee: satellite6-bugs <satellite6-bugs>
Status: NEW --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: aruzicka, oezr, patalber
Target Milestone: UnspecifiedKeywords: Patch, Triaged
Target Release: UnusedFlags: aruzicka: needinfo? (wpinheir)
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Waldirio M Pinheiro 2020-09-24 21:05:00 UTC
Description of problem:
Working in a case where the usergroup feature was not working as expected, instead the ldapfluff method "user_list" bring the uid, was returning the first and last name. For example, instead of "waldirio" was returning "waldirio pinheiro", that said, the match with the user account was failing and not working properly.

Version-Release number of selected component (if applicable):
6.6

How reproducible:
100% on the customer environment. They have openldap implemented.

Steps to Reproduce:
1. foreman-rake console
2. creating the connection and then proceeding with the method call
3. conn.user_list('satellite_grp')

Actual results:
=> ["waldirio pinheiro"]

Expected results:
=> ["waldirio"]

Additional info:

Comment 2 Ondřej Ezr 2020-10-05 11:15:59 UTC
Created redmine issue https://projects.theforeman.org/issues/30974 from this bug

Comment 5 Brad Buckingham 2023-05-08 12:47:51 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 8 Brad Buckingham 2023-06-12 23:10:52 UTC
Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation.