Siebel is Sending LDAP Unbind & Timeout Error If LDAP is Not Responding in 10 Secs with Error "SBL-SEC-10018: Timed out"
(Doc ID 2707916.1)
Last updated on NOVEMBER 03, 2020
Applies to:Siebel CRM - Version 19.9 to 20.10 [Release V17]
Information in this document applies to any platform.
Siebel is sending an Unbind request after 10 seconds, and failing. If the ldap bind happens with in 10 secs, then all looks fine. In case if there is any delay connecting to LDAP and if bind is not responding with in 10 secs, Siebel is giving server busy error and OM log reported with below errors:
GenericLog GenericError 1 00000e055df76b61:0 2020-02-02 10:19:57 (secmgr.cpp (2773) err=4597538 sys=0) SBL-SEC-10018: Timed out
GenericLog GenericError 1 00000e055df76b61:0 2020-02-02 10:19:57 (secmgr.cpp (2845) err=4597521 sys=0) SBL-SEC-10001: An internal error has occurred within the authentication subsystem
The issue can be reproduced at will with the following steps:
1. Install siebel
2. Integrate Siebel with LDAP
3. If the user authentication(ldap ind) at LDAP side is taking more than 10 secs, then it is failing to login with timeout error
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