My Oracle Support Banner

OAM 11g: Not able to login to oamconsole after disabling weblogic listen open port (Doc ID 1467276.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Access Manager - Version 11.1.1.5.0 and later
Information in this document applies to any platform.
Setup Weblogic to listen to both open and SSL port. After disabling open port, however, you can no longer login to oamconsole. Login to Weblogic console , however, continue to work.

Example:
https:///console -> Login works
https:///oamconsole -> Login failed

If you re-enable Weblogic's open port, then you can login to oamconsole without issue

Symptoms

Not able to login to oamconsole once you disable the Weblogic's open port. From the diagnostic log, you see the exception is on the open port which has been disabled:

[2012-04-17T10:29:22.667-07:00] [AdminServer] [ERROR] [OAMSSA-20005]
[oracle.oam.user.identity.provider] [tid: [ACTIVE].ExecuteThread: '5' for
queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid:
6a857fcca9778282:-6a595e82:136c153199d:-8000-00000000000000e1,0] [APP:
oam_admin#11.1.1.3.0] Error initializing User/Role API : {0}.[[
oracle.security.am.engines.common.identity.provider.exceptions.IdentityProvid
erException
at
oracle.security.am.engines.common.identity.provider.util.LDAPConfigurator.get
IdStore(LDAPConfigurator.java:557)
at ...
...
Caused by: javax.naming.CommunicationException: <weblogic host>:<weblogic open port>
[Root exception is java.net.ConnectException: Connection refused]
at com.sun.jndi.ldap.Connection.<init>(Connection.java:198)
at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:116)
at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1580)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2678)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:296)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:175)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:193)
at
com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:136)
at
com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:66)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
at
oracle.security.idm.providers.stdldap.LDConnectionPool.createContext(LDConnec
tionPool.java:414)
at
oracle.security.idm.providers.stdldap.LDConnectionPool.createConnection(LDCon
nectionPool.java:381)
at
oracle.security.idm.providers.stdldap.LDConnectionPool.createConnections(LDCo
nnectionPool.java:374)
at
oracle.security.idm.providers.stdldap.LDConnectionPool.<init>(LDConnectionPoo
l.java:154)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccess
orImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstruct
orAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at
oracle.security.idm.providers.stdldap.LDIdentityStoreFactory.createPoolInstan
ce(LDIdentityStoreFactory.java:657)
... 95 more

 

Changes

 Using embeded ldap, and disabled the open port. 

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!


In this Document
Symptoms
Changes
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.