E1: LDAP: How to use a custom LDAP attribute for the E1 username with OAM Single Sign On configurations
Last updated on OCTOBER 15, 2015
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
Context: When configuring Single Sign On with OAM for E1 JAS instances, there is a step in OAM where a specific HTTP Header is configured for all connections reaching JAS.
This header named JDE_SSO_UID must contain the E1 username to be passed to JAS. This is done using OAM variables. The variable used in the guides is $user.userid which represents the attribute in LDAP used as username for credential validations. So if LDAP is configured to use email as the usernames, then that is the value passed by $user.userid.
Issue: How to use a custom LDAP attribute for the E1 username instead of the LDAP userid when configuring Single Sign On for JAS with OAM?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms