LDAP/ADSI Security Adapter authentication fails after the upgrade to 184.108.40.206 (IP2014)
Last updated on DECEMBER 25, 2017
Applies to:Siebel CRM - Version 220.127.116.11 [IP2014] and later
Information in this document applies to any platform.
Some customers have implemented LDAP (or ADSI) security adapter authentication in previous Siebel 8.1.1.* environment and it works without problem. Then Siebel 18.104.22.168 (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.
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