| 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: | |
|
Description
fjayalat
2016-03-14 02:55:10 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 ~~ 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=". This content is now live on the Customer Portal. Closing. |