CCB user login issue in Weblogic cluster / SSO environment (Doc ID 1954843.1)

Last updated on MARCH 11, 2024

Applies to:

Symptoms

<Environment>

CCB v2.4.0.2/FW 4.2.0.2 and clustered Weblogic .

2  Managed Servers within a Cluster.

Weblogic 1 and CCB 1 is on server A ; Weblogic 2 and CCB 2 is on server.

Windows Active Directory is used as SSO.

<Issue Description>

(1) SYSUSER can login

(2) Create a User1 in CCB

User1 did login first by Weblogic-1.
User1 can login CCB by Weblogic-1.
User1 cannot login CCB by Weblogic-2.

Got this error is log,

- 925402-758-1 2014-11-25 18:01:52,414 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR (support.context.SessionExecutable) Caught exception from SessionExecutable.execute()
- 323088-153-1 2014-11-25 18:01:52,415 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR (web.services.InitializeUserInfoTag) Unable to emit user info

(3) Create a User2 in CCB.

User2 did login first from Weblogic-2.
User2 canot login CCB by Weblogic-1.
User1 can login CCB by Weblogic-2.

Got this error is log,

- 316760-75654-1 2014-11-25 18:29:50,589 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR (support.context.SessionExecutable) Caught exception from SessionExecutable.execute()
- 841387-12848-1 2014-11-25 18:29:50,590 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR (web.services.InitializeUserInfoTag) Unable to emit user info

<Workaround>

Issue was temporarily fixed by removing F1_SECURITY_HASH (on table SC_USER) value of User1 and User2.

SYSUSER has no F1_SECURITY_HASH value by default.

Changes

Cause

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