Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1317337

Summary:	Satellite 6.1 Documentation needs to be corrected. Related to the section " 20.4. Using Active Directory Directly"
Product:	Red Hat Satellite	Reporter:	fjayalat
Component:	Documentation	Assignee:	Stephen Wadeley <swadeley>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Russell Dickenson <rdickens>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1.7	CC:	adahms, arahaman, fjayalat, swadeley
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-16 04:21:02 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 fjayalat 2016-03-14 02:55:10 UTC

Description of problem:

Procedure mentioned in satellite 6.1 documentation  "20.4. Using Active Directory Directly" is incorrect. Would be good , if we can fix the issue.

Correct procedure can be found in the kcs below :
https://access.redhat.com/solutions/2197571



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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:

Comment 1 Ashfaqur Rahaman 2016-03-18 01:44:33 UTC

Procedure 20.1. To Configure LDAP Authentication 

--> Base DN: the top level domain name of your LDAP directory. For example:
~~
cn=users,cn=accounts,dc=redhat,dc=com
~~

It should be 
~~
dc=redhat,dc=com
~~

Comment 2 Stephen Wadeley 2016-05-03 14:48:29 UTC

Hello

comment 1 refers to Step 4 in

Procedure 20.1. To Configure LDAP Authentication

which has "cn=users,cn=accounts,dc=redhat,dc=com"


https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/User_Guide/chap-Red_Hat_Satellite-User_Guide-Configuring_External_Authentication.html#proc-Red_Hat_Satellite-User_Guide-Using_LDAP-To_Configure_LDAP_Authentication


In this table:

Table 20.1. Example Settings for Active Directory LDAP Connection

there is also "Base DN 	CN=Users,DC=example,DC=COM "

and in this table:

Table 20.2. Example settings for FreeIPA LDAP Connection

there is "Base DN 	cn=users,cn=accounts,dc=example,dc=com "

= = =

I suppose that in each case "Base DN" field should only contain "DC=example,DC=COM", no "cn=".

Comment 11 Andrew Dahms 2016-06-16 04:21:02 UTC

This content is now live on the Customer Portal.

Closing.