My Oracle Support Banner

OBIEE 11g: Can Not Log In with Error: "Unable to Sign In An error occurred during authentication." and LIBOVD-60143 When One or several of Multiple Authentication Providers is Down Or Not Reachable (Doc ID 2379482.1)

Last updated on MAY 01, 2018

Applies to:

Business Intelligence Server Enterprise Edition - Version 11.1.1.7.0 to 11.1.1.9.180116 [Release 11g]
Information in this document applies to any platform.

Symptoms

You have configured OBIEE 11g to use multiple authentication providers (for exampleg two MSADs in addition to the default authentication provider). You set the Virtualize parameter to TRUE and created users in all the authentication providers. You confirmed that all users and Groups from all Authentication Providers can be seen in Weblogic Server. You confirmed that users from all the Authentication Providers can log in to OBIEE and that the administration user specified when you installed OBIEE can log in to OBIEE.

But, when one (or several ) of the authentication providers goes down or not reachable, no one can log in to OBIEE including the administration user of default authentication provider (DefaultAuthenticator).  You saw the following error in the OBIEE log in screen:

Unable to Sign In
An error occurred during authentication.
Try again later or contact your system administrator

In bi_serverx-diagnostic.log, you find LIBOVD-60143 error like below:

[2018-01-09T13:36:09.177+09:00] [bi_server1] [ERROR] [LIBOVD-60143] [oracle.ods.virtualization.exception] [tid: [ACTIVE].ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 1b02a616821dd251:78901ba3:160d8affd61:-8000-0000000000000003,1:26991:73:1:6:1] [APP: bisecurity#11.1.1] [J2EE_APP.name: bisecurity_11.1.1] [J2EE_MODULE.name: bisecurity] [WEBSERVICE.name: SecurityWebService] [WEBSERVICE_PORT.name: SecurityWebServicePort]{0} Unable to create connection to {1} as {2}[[
javax.naming.CommunicationException: LDAP server IP:389 [Root exception is java.net.ConnectException: Connection timed out]

 

You have changed adapters.os_xml as Document 1417583.1 suggested, but symptom persists.

You also tried to increase wls:connect-timeout in config.xml, but symptom persists.

Changes

One (or several ) of multiple authentication providers is down or not reachable.

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.