Ldap Utility: BindAsAppUser Fails Due To Invalid Password Error SBL-DAT-00565
(Doc ID 1237883.1)
Last updated on MARCH 03, 2020
Applies to:Siebel System Software - Version 188.8.131.52 SIA  and later
Siebel CRM - Version 184.108.40.206  and later
Information in this document applies to any platform.
*** Currency Review Completed 03-MAR-2020 with edits ***
When customer attempts to authenticate Siebel Application Object Manager (AOM) with LDAP or AD authentication , the Siebel AOM application fails to come up and the following errors are recorded in the logs under $SIEBEL_ROOT/siebsrvr/log directory (Windows) or $SIEBEL_ROOT/siebsrvr/enterprises/enterprisename/siebelservername/log directory (UNIX) for the AOM logs that failed LDAP authentication:
1. Setup Siebel Application Object Manager with LDAP or ADSI authentication.
2. Make sure that standard LDAPSecAdpt or ADSISecAdpt profile is used.
3. Check to see if the Siebel Application Object Manager with LDAP or ADSI authentication is coming up properly.
Note: This will happen only when using standard LDAPSecAdpt profile to authenticate against the directory server
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