Filtered Out LDAP User Gets Integrated to Agile Along With the User Group Which the User Belongs To (Doc ID 2279792.1)

Last updated on JUNE 23, 2017

Applies to:

Oracle Agile PLM Framework - Version 9.3.5.0 and later
Information in this document applies to any platform.

Symptoms

Actual Behavior

Filtered out LDAP User gets integrated to Agile along with the User Group which the user belongs to

Expected Behavior

Filtered out user not to be integrated to Agile

Steps to Reproduce

  1. In the LDAP server, create below users and user groups:
    Users: user1, user2, user3, user4
    User Group:
    group1 - user1, user2
    group2 - user3, user4
  2. Set below value in agile.properties to true:
    auth.ldap.group.enabled=true
  3. Restart Agile Application Server
  4. Login to Java Client, and set below filter to LDAP configuration:
    Search Filter:(&(objectclass=person)(!(cn=user1)))
  5. Preview. Confirm that only user2, user3, user4 shows up
  6. Add below filter to Java Client LDAP setting:
    Group Filter:(objectclass=group)
    Group Membership: (&(uniquemember=%M)(objectclass=groupofuniquenames))
  7. Preview. See user1 also shows up

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms