My Oracle Support Banner

OBIEE 12c: Cannot Login To OBI Server After Configuring LDAP Authenticator For SLDAP (636), error: javax.net.ssl.SSLHandshakeException: Server chose TLSv1, but that protocol version is not enabled or not supported by the client (Doc ID 2377401.1)

Last updated on JUNE 10, 2018

Applies to:

Business Intelligence Suite Enterprise Edition - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

 

Login To OBI Server After Configuring LDAP Authenticator For SLDAP fails.  SLDAP (Secure Lightweight Directory Access Protocol )

 ( https://docs.oracle.com/middleware/bi12214/biee/BIESC/GUID-B3F876BE-9344-4803-9B99-5A4C64F68D6C.htm#GUID-89E3664C-02F2-48BF-8328-B928E6985F8A )

The error message in the bi_server1-diagnostics.log :-

[2018-01-09T09:25:43.205-05:00] [bi_server1] [NOTIFICATION] [JPS-06134] [oracle.jps.upgrade] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: b2d1da52-9a15-4cd2-bcfa-e576b327c35e-00000011,0] [APP: bicomposer] [partition-name: DOMAIN] [tenant-name: GLOBAL] Migration of Credential Store data completed, Time taken for migration is 00:00:00 "bi_server1-diagnostic.log" 668L, 185648C at oracle.ods.virtualization.engine.chain.GlobalServicesInterface.runGet(GlobalServicesInterface.java:135) at oracle.ods.virtualization.operation.SearchOperation.process(SearchOperation.java:203) ... 53 more Caused by: javax.naming.CommunicationException: simple bind failed: xxxx.xxxx.xxx.com:636 [Root exception is javax.net.ssl.SSLHandshakeException: Server chose TLSv1, but that protocol version is not enabled or not supported by the client.]

SOLUTION

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


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