Wednesday, February 11, 2015

OAM Console Issue after Upgrade

We are seeing following issue in OAM Console, After Upgrade from 11g R2 to 11g R2 PS2.

java.lang.SecurityException: MBean operation access denied. MBean: oracle.oam:type=Config Operation: retrieveMapPropertyArray(java.lang.String) Detail: Access denied. Required roles: Admin, executing subject: principals=[weblogic, OAMSystemAdminGroup]
Error
MBean operation access denied. MBean: oracle.oam:type=Config Operation: retrieveMapPropertyArray(java.lang.String) Detail: Access denied. Required roles: Admin, executing subject: principals=[weblogic, OAMSystemAdminGroup]
Error
Access denied. Required roles: Admin, executing subject: principals=[weblogic, OAMSystemAdminGroup]


Solution:

1. Log in to the WebLogic Administration Server Console
2. In the left pane of the console, click Security Realms.
3. On the Summary of Security Realms page, click myrealm under the Realms table.
4. On the Settings page for myrealm, click the Roles & Policies tab.
5. On the Realm Roles page, expand the Global Roles entry under the Roles table. This brings up the entry for Roles.
6. Click the Roles link to go to the Global Roles page.
7. On the Global Roles page, click the Admin role to go to the Edit Global Role page:
8. On the Edit Global Roles page, under Role Conditions, click Add Conditions.
9. On the Choose a Predicate page, select Group from the predicates list and click Next.
10. On the Edit Arguments Page, specify the admin Group/User specified in OUD store (while setting it to system store in oamconsole) in the Group Argument field and click Add.
11. Click Finish to return to the Edit Global Rule page.
12. The Role Conditions now show the the admin group specified in OUD store Group as an entry.

13. Click Save to finish adding the Admin role to the admin group specified in OUD store Group. 

No comments:

Post a Comment

Other Posts