OPSS - ReassociateSecurityStore Fails With COMMAND FAILED Due To An Unknown Reason trying to Reassociate Security Store to new LDAP
(Doc ID 2170145.1)
Last updated on MARCH 01, 2023
Applies to:
Oracle Platform Security for Java - Version 11.1.1.7.0 and laterInformation in this document applies to any platform.
Symptoms
On OPSS 11.1.1.7.0 version, Java Platform Security
There was already an OID associated with their domain, as Policy Store, working fine for some time.
The goal is change the current OID environment, and perform the reassociation to the new OID.
When they try to use the reassociateSecurityStore command fails with COMMAND FAILED due to an unknown reason.
wls:/<adminserver>/serverConfig> reassociateSecurityStore(domain="<DOMAIN_NAME>", admin="cn=<USERNAME>", password="<PASSWORD>", ldapurl="ldap://<LDAP_HOST>:<LDAP_PORT>", servertype="OID", jpsroot="cn=<JPSROOT>", join="true")
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)
Starting policy store reassociation.
COMMAND FAILED due to an unknown reason, Check the stack trace for details
Traceback (innermost last):
File "<console>", line 1, in ?
File "/<MW_HOME>/oracle_common/common/wlst/jpsWlstCmd.py", line 1569, in reassociateSecurityStore
File "/<MW_HOME>/oracle_common/common/wlst/jpsWlstCmd.py", line 1501, in reassociateSecurityStoreImpl
File "/<MW_HOME>/oracle_common/common/wlst/jpsWlstCmd.py", line 1390, in reassociateService
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at javax.management.remote.rmi.RMIConnectionImpl_1036_WLStub.invoke(Unknown Source)
at weblogic.management.remote.common.RMIConnectionWrapper$16.run(ClientProviderBase.java:918)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at weblogic.management.remote.common.RMIConnectionWrapper.invoke(ClientProviderBase.java:916)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:993)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)
Starting policy store reassociation.
COMMAND FAILED due to an unknown reason, Check the stack trace for details
Traceback (innermost last):
File "<console>", line 1, in ?
File "/<MW_HOME>/oracle_common/common/wlst/jpsWlstCmd.py", line 1569, in reassociateSecurityStore
File "/<MW_HOME>/oracle_common/common/wlst/jpsWlstCmd.py", line 1501, in reassociateSecurityStoreImpl
File "/<MW_HOME>/oracle_common/common/wlst/jpsWlstCmd.py", line 1390, in reassociateService
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at javax.management.remote.rmi.RMIConnectionImpl_1036_WLStub.invoke(Unknown Source)
at weblogic.management.remote.common.RMIConnectionWrapper$16.run(ClientProviderBase.java:918)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at weblogic.management.remote.common.RMIConnectionWrapper.invoke(ClientProviderBase.java:916)
at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:993)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
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 |
| Cause |
| Solution |