Bug 1468104

Summary: [Sat6.2] LDAP Groups base DN not visible in CLI through command "#hammer auth-source ldap info"
Product: Red Hat Satellite Reporter: satish sherkar <ssherkar>
Component: HammerAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Jan Hutař <jhutar>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.10CC: aagrawal, dhlavacd, jcallaha, jhutar, mhulan, tstrachota
Target Milestone: 6.4.0Keywords: Patch, Triaged
Target Release: Unused   
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: 2018-10-16 19:13:09 UTC 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 satish sherkar 2017-07-06 05:18:25 UTC 
[Sat6.2] LDAP Groups base DN not visible in CLI through command "#hammer auth-source ldap info"

Version-Release number of selected component (if applicable):Satellite 6.2.x

>> Description of problem:

>> How reproducible:
A RHEL 7.2 installation with Satellite 6.2.10 configured to use external LDAP authentication (created using hammer)

In Satellite WebUI Administer >> LDAP authentication >> authentication source >> Account >> Here we can set Groups base DN but if we check this info from "#hammer auth-source ldap info --name "name" then it will not visible."

>> Actual results:

 Group base DN is not visible through command on Satellite: #hammer auth-source ldap info --name "name"

>> Expected results:

 Group base DN should be visible through command on Satellite: #hammer auth-source ldap info --name "name" like it visible in Satellite WebUI Administer >> LDAP authentication >> authentication source >> Account.
Comment 3 Satellite Program 2017-07-14 08:13:17 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20227 has been resolved.
Comment 5 Bryan Kearney 2018-10-16 19:13:09 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:2927