E1: LDAP: SEC: Long User ID Works For Some Web Users But Not Others, Security Kernel Log States: 'Truncating value of E1-UserID LDAP attribute:<sAMAccountName>'
(Doc ID 2623607.1)
Last updated on JANUARY 24, 2024
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Having or after implementing the Long User ID functionality, some of the E1 users are not able to login. For those users that cannot login, the following message is recorded into the Security Kernel log files:
Changes
Scenario 1: Long user ID feature has been implemented and than LDAP authentication has been enabled, where E1USRIDATR was mapped to a LDAP attribute for which the value was longer that 10 characters and the truncation of the value matched an existing record in F0092L, ULLUSER column.
Scenario 2: The values of the LDAP attribute mapped to E1USRIDATR have been changed on LDAP server side and also the value of the LDAP attribute mapped to EUSRIDATR has been changed (mapping in P95928 was changed to another LDAP attribute or the value of the existing LDAP attribute has been altered).
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |