WLSTException: java.lang.SecurityException: MBean operation access denied

When trying to export the metadata, probably using something such as exportMetadata(application='OIMMetadata',server='oim_server1',toLocation='/home/oracle/Oracle/Middleware/tmp'), I would receive the following error:
November 30, 2014
OIM-11gPlugins

Executing operation: exportMetadata.

Traceback (innermost last):
File "", line 1, in ?
File "/home/oracle/Oracle/Middleware/oracle_common/common/wlst/mdsWLSTCommands.py", line 263, in exportMetadata
File "/home/oracle/Oracle/Middleware/oracle_common/common/wlst/mdsWLSTCommands.py", line 816, in executeAppRuntimeMBeanOperation
File "/home/oracle/Oracle/Middleware/oracle_common/common/wlst/mdsWLSTCommands.py", line 1097, in saveStackAndRaiseException
WLSTException: java.lang.SecurityException: MBean operation access denied.
MBean: oracle.mds.lcm:name=MDSAppRuntime,type=MDSAppRuntime,Application=OIMMetadata,ApplicationVersion=11.1.2.0.0
Operation: exportMetadata(java.lang.String, boolean, [Ljava.lang.String;, [Ljava.lang.String;, [Ljava.lang.String;, boolean, boolean, boolean, boolean, java.lang.String, java.lang.String, java.lang.String)
Detail: Access denied. Required roles: Admin, Operator, executing subject: principals=[SYSTEM ADMINISTRATORS, xelsysadm] MDS-91009: Operation "exportMetadata" failure. Use dumpStack() to view the full stacktrace.
wls:/OIM11gR2PS2_domain/serverConfig> exportMetadata(application='OIMMetadata',server='oim_server1',toLocation='/tmp')

wls:/OIM11gR2PS2_domain/serverConfig> WLST lost connection to the WebLogic Server that you were connected to, this may happen if the server was shutdown or partitioned. You will have to re-connect to the server once the server is available. Disconnected from weblogic server: AdminServer


SOLUTION

Turns out that I was using the weblogic and not the xelsysadm username. This can be confusing because the export of the metadata could be used with the weblogic username. Either way, if you're getting this issue, use the other username.

wls:/offline> connect()
Please enter your username :xelsysadm
Please enter your password :
Please enter your server URL [t3://localhost:7001] :t3://localhost.localdomain:14000
Connecting to t3://localhost.localdomain:14000 with userid xelsysadm ...
Successfully connected to managed Server 'oim_server1' that belongs to domain 'OIM11gR2PS2_domain'.

Warning: An insecure protocol was used to connect to the server. To ensure on-the-wire security, the SSL port or Admin port should be used instead.

wls:/OIM11gR2PS2_domain/serverConfig

About the author

Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.
Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles

Comments

Other Posts

NameID element must be present as part of the Subject in the Response message

ShibbolethSAML

August 7, 2018
Created by: Daniel Redfern
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...

HOW TO provision AD group membership from OpenIDM

OpenIDMICFAD-connector

June 15, 2018
Created by: Daniel Redfern
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

ICFIDMOpenIDMOpenICF

November 8, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

org.forgerock.script.exception.ScriptCompilationException: missing ; before statement

IDMsync.confforgerockopenidm

November 8, 2017
Created by: Daniel Redfern
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statemen

OpenIDMsync.confForgeRock

September 17, 2017
Created by: Daniel Redfern
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

Caused by: org.forgerock.json.resource.BadRequestException: Target does not support attribute groups

OpenIDMForgeRockICFConnector

September 17, 2017
Created by: Daniel Redfern
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

OpenIDMForgeRockICFConnectorAD

September 17, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_g

OpenIDMIDMGoogleGoogle-AppsICFreconciliation

September 12, 2017
Created by: Daniel Redfern
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...

forgerock-openidm-encryptedjwt-error

OpenIDMIDMForgeRockJWTIAM

August 29, 2017
Created by: Daniel Redfern
Received the JWT error
Read More...

Unexpected character ('¾' (code 190)): expected a valid value

ForgeRock-OpenIDMOpenIDMIDMKeystore

June 25, 2017
Created by: Daniel Redfern
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
Read More...