Unable to Map LDAP ID With Page Two Attribute When Using GenericLDAP

(Doc ID 2374547.1)

Last updated on MARCH 16, 2018

Applies to:

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


Actual Behavior

Unable to map LDAP ID with Page Two attribute for GenericLDAP

Expected Behavior

Able to map LDAP ID with Page Two attribute for GenericLDAP

What is Working

Issue does not happen when using Active Directory


The issue can be reproduced at will with the following steps:

  1. Login to Java Client as admin user
  2. Enable Users.Page Two.Text13 field and change Name to: CountryCode
  3. Goto Admin tab > Settings > Server Settings > LDAP
  4. Double click and open LDAP configuration for GenericLDAP
  5. Goto User-LDAP Attributes Mapping, and click New mapping entry
  6. Map Agile ID: CountryCode to LDAP ID: countryCode, and OK
  7. Add the Page Two attribute in getSchemaInfo() in Groovy script
  8. Run Refresh User From LDAP Directory
    Result: CountryCode field is not updated




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