"Ldap Utility: BindAsAppUser failed for some unknown reasons, Can't contact LDAP server" Error Encountered When Implementing LDAPSecAdpt To Connect To Directory Server On SSL Port
(Doc ID 2761426.1)
Last updated on OCTOBER 01, 2021
Applies to:Siebel CRM - Version 17.0 [IP2017] and later
Information in this document applies to any platform.
When attempting to access Siebel FINS application post changing ADSISecAdpt to LDAPSecAdpt, the Siebel FINS application fails to load and the following error occurs in Siebel Application Object Manager logs:
SecMgrLog Debug 5 0000000860502e54:0 2021-03-16 20:59:11 port = 636
SecMgrLog Debug 5 0000000860502e54:0 2021-03-16 20:59:11 ssldatabase =
GenericLog GenericError 1 0000000860502e54:0 2021-03-16 20:59:11 (secmgr.cpp (2857) err=4597521 sys=0) SBL-SEC-10001: An internal error has occurred within the authentication subsystem for the Siebel application. Please contact your system administrator for assistance.
ObjMgrSessionLog Error 1 0000000860502e54:0 2021-03-16 20:59:11 (physmod.cpp (9821)) SBL-DAT-00565: An internal error has occurred within the authentication subsystem for the Siebel application. Please contact your system administrator for assistance.
The issue can be reproduced at will with the following steps:
1. Setup LDAPSecAdpt with Siebel application
2. Make sure that LDAPSecAdpt profile is defined for SSL port configuration with AD server or any directory server.
3. Check to see if the Siebel application is accessible with the SSL.
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