LDAP/ADSI Security Adapter authentication fails after the upgrade to 8.1.1.14 (IP2014) (Doc ID 1982608.1)

Last updated on JANUARY 02, 2020

Applies to:

Symptoms

Some customers have implemented LDAP (or ADSI) security adapter authentication in previous Siebel 8.1.1.* environment and it works without problem. Then Siebel 8.1.1.14 (IP2014) is applied and the necessary upgrade processes, including Incremental Repository Merge (IRM), are done. When Siebel Server is restarted and the web client attempts to connect, it fails with the following error message.

"The server you are trying to access is either busy or experiencing difficulties. Please close the Web browser, open a new browser window, and try logging in again. [hh:mm:ss]"

Also the corresponding object manager log file shows the error message something like this.

Case 1) SBL-SEC-00101: An error occurred loading the Siebel authentication subsystem configuration parameters from the configuration store. Please contact your system administrator to check parameter LDAPSecAdpt::Application Password.

Case 2) SBL-DAT-00565: An internal error has occurred within the authentication subsystem for the Siebel application. Please contact your system administrator for assistance.

Case 3) SBL-DAT-00446: You have entered an invalid set of logon parameters. Please type in your logon parameters again

Note: Depending on the security adapter, component and the type of the password parameter, actual error may be different from the above.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.