SOA Server Authentication Error With Correct Credential Configuration

SOA Server Authentication Error With Correct Credential Configuration

With SOA and BAM deployed on two separate WLS domain.

Security Exception Observed on RMI invocation from SOA to BAM ADC EJB

From SOA Server Log:

Caused by: java.lang.SecurityException: <strong>[Security:090398]</strong>Invalid Subject: principals=weblogic, Administrators
...
Caused by: java.lang.SecurityException: <strong>[Security:090398]</strong>Invalid Subject: principals=weblogic, Administrators
at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:835)
...

From BAM Server Log:

<Jan 30, 2009 4:59:40 PM PST> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.jndi.internal.AdminRoleBasedDispatchServerRef@9, implementation: 'weblogic.jndi.internal.RootNamingNode@4e229e', oid: '9', implementationClassName: 'weblogic.jndi.internal.RootNamingNode'
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=weblogic, Administrators.
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=weblogic, Administrators
at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:835)
at weblogic.security.service.SecurityServiceManager.getSealedSubjectFromWire(SecurityServiceManager.java:524)
at weblogic.rjvm.MsgAbbrevInputStream.getSubject(MsgAbbrevInputStream.java:315)
at weblogic.rmi.internal.BasicServerRef.acceptRequest(BasicServerRef.java:875)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:310)
Truncated. see log file for complete stacktrace

You must set up Trusted Domain on both Oracle WebLogic Server domains.

Go to Oracle WebLogic Server Administration Console>Respected Domainssoainfra or bam>Securityand do the following:

1. Navigate to Home>Domain>Security, and checkCross Domain Security Enabled.

2. Click Advanced, enter the desired password in theCredential and Confirm Credential fields, and click Save.

3. Repeat this configuration change for both domains using the same password value.

4. Restart both Oracle WebLogic Servers.