My Oracle Support Banner

WNA OC4J_SECURITY...Unable To Communicate With The Directory Or Naming Service (Doc ID 468705.1)

Last updated on JULY 11, 2013

Applies to:

Oracle Application Server Single Sign-On - Version to [Release 10gR2 to 10gR3]
Information in this document applies to any platform.
***Checked for relevance on 11-JUL-2013***


After running SSOCA to configure WNA, the OC4J_SECURITY will not start.

Log file $ORACLE_HOME/opmn/logs/OC4J~OC4J_SECURITY~default_island~1 with debug turned on shows:

[InfraStructureDatabase]=, [EMConfigData]=, IMReposAdminSupported=True, OIDport=389,
DatabaseManagedClusterSupport=true, MODOSSO.LaunchSuccess=true}
07/11/26 16:34:27 Broken pipe
07/11/26 16:34:27 The system is unable to communicate
with the directory or naming service.

07/11/26 16:34:27 at
07/11/26 16:34:27 at
07/11/26 16:34:27 Caused by: javax.naming.CommunicationException: oidserver.domain:389 [Root
exception is SSL handshake failed:

07/11/26 16:34:27 ... 25 more
07/11/26 16:34:27 Caused by: SSL handshake
failed: SSLConnectionClosedGraceful
07/11/26 16:34:27 at Source)
07/11/26 16:34:27 at Source)
07/11/26 16:35:37 Authentication Failed
07/11/26 16:35:37 Authentication: FAILED.
07/11/26 16:35:37 JAAS-OC4J: Membership check for group: {{PUBLIC}} failed for user:


Set up WNA by running command:  ssoca -mode wna


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

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