SSO Login Via Portal or OIDDAS Fails When One Node in Identity Management 10g High Availability Cluster is Shut Down

(Doc ID 469053.1)

Last updated on FEBRUARY 27, 2017

Applies to:

Oracle Fusion Middleware High Availability - Version 10.1.2.0.0 to 10.1.4.3.0 [Release AS10gR2 to AS10gR3]
Information in this document applies to any platform.
Oracle Application Server Identity Management running in a highly available, active-active Identity Management Cluster (IMHA)


***Checked for relevance on 06-Jan-2014***


Symptoms

An SSO login via Portal or OIDDAS hangs:

The error_log of the active Identity Management (SSO) node (node1) has following entries

Executing 'opmnctl status' against the running OID and SSO instances shows all components to be 'Alive'.

If the HTTP Server of the active Identity Management (SSO) node is restarted login to SSO is successful in all cases

If the OID or SSO of node2 is stopped using opmnctl then the node1 works fine.

Changes

One of the nodes (host machines) of a high availability Identity Management Cluster is deliberately shutdown or unexpectedly crashes (without first cleanly shutting down the OracleAS processes.) The Single Sign-On functionality should nevertheless continue to work because the other node or nodes in the cluster remain up and running. As described above, in practice this is not always the case.

Cause

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 hundreds of Community platforms