Bug 1381674 - [DOCS] LDAP - filters no longer valid for UserUIDAttribute = dn
Summary: [DOCS] LDAP - filters no longer valid for UserUIDAttribute = dn
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.3.0
Hardware: All
OS: All
medium
high
Target Milestone: ---
: ---
Assignee: brice
QA Contact: Chuan Yu
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-04 17:20 UTC by Matthew Robson
Modified: 2017-01-18 10:03 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-22 00:39:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Matthew Robson 2016-10-04 17:20:21 UTC
Document URL:
https://access.redhat.com/documentation/en/openshift-container-platform/3.3/single/installation-and-configuration/#running-ldap-sync

Section Number and Name: 
13.5. SYNC EXAMPLES

Describe the issue:
A change went into 3.3 which prevents filters being used when UserUIDAttribute = dn

https://github.com/openshift/ose/commit/9351adc9cb35ee67ab82659c165dcb4f3799e33d 

Suggestions for improvement: 
All of our doc currently specify a filter with UserUIDAttribute dn

Additional information:
The above commit removes all of the filers in question from the test YAML files.

    usersQuery:
        baseDN: "ou=users,dc=example,dc=com"
        scope: sub
        derefAliases: never
        filter: (objectclass=inetOrgPerson)
        pageSize: 0
    userUIDAttribute: dn 6

filter: (objectclass=inetOrgPerson) is no longer valid.

Would get an error during sync;

error: validation of LDAP sync config failed: usersQuery.filter: Invalid value: "(\u0026(objectclass=user)(memberof=cn=Super_Admins,dc=company,dc=com))": cannot specify a filter when using "dn" as the UID attribute

Comment 1 Timothy 2016-10-10 03:23:02 UTC
Matthew:

Your suggestion for improvement is "All of our doc currently specify a filter with UserUIDAttribute dn", are you suggesting that mentions of using this filter with the UserUIDAttribute DN simply need to be removed? 

Or will the impact on OpenShift users be more significant than that? Is there a new DN that they must specify instead, one that allows them to use filters? Are there other manual changes that must now take place? 

Any additional information you can point me to would be very helpful, thank you.

Comment 2 Matthew Robson 2016-10-12 12:56:08 UTC
Correct, they need to be removed.  If you look at the above commit, you can see all of the 'filters' were removed as part of this change.

There are no filters allowed when using DN for UserUIDAttribute.  

The recommendation for finer grained filtering is to use the already documented whitelist / blacklist approach.

Comment 8 brice 2016-10-31 05:42:42 UTC
Tim's PR has merged:

https://github.com/openshift/openshift-docs/pull/3077

Plus, I created a follow up PR to address the one he missed:

https://github.com/openshift/openshift-docs/pull/3132

Moving this BZ to release pending


Note You need to log in before you can comment on or make changes to this bug.