'Request could not be handled' error reverting a Role that has been moved to a different Role Set in RSA Identity Governance & Lifecycle
Originally Published: 2020-03-30
Article Number
Applies To
RSA Version/Condition: 7.1.0, 7.1.1,7.2.0
Issue
The request could not be handled
Once this error occurs any attempt to access this role (Roles > Roles > {Role name}) results in the same error. The Role is permanently inaccessible.
The aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/aveksaServer.log) shows the following ERROR level log message:
ERROR (default task-17) [com.aveksa.gui.core.MainManager] 03/04/2020 09:13:30.535 ERROR (default task-17)
[com.aveksa.gui.core.MainManager] java.lang.NullPointerException
at com.aveksa.gui.pages.admin.globalRole.detail.GlobalRoleDetailHelper.makeRoleSetFld(GlobalRoleDetailHelper.java:1119)
at com.aveksa.gui.pages.admin.globalRole.detail.GlobalRoleDetailHelper.printContent(GlobalRoleDetailHelper.java:645)
at com.aveksa.gui.pages.admin.globalRole.detail.main.GlobalRoleMainPageView.printDetails(GlobalRoleMainPageView.java:78)
at com.aveksa.gui.pages.admin.globalRole.detail.main.GlobalRoleMainPageView.printContent(GlobalRoleMainPageView.java:60)
at com.aveksa.gui.pages.admin.globalRole.detail.main.GlobalRoleMainPageView.printContent(GlobalRoleMainPageView.java:45)
at com.aveksa.gui.pages.base.view.MainPageView.printPageContentTable(MainPageView.java:304)
at com.aveksa.gui.pages.base.view.MainPageView.handlePartialPage(MainPageView.java:174)
at com.aveksa.gui.pages.base.view.MainPageView.handleRequest(MainPageView.java:49)
at com.aveksa.gui.pages.base.data.PageData.drawView(PageData.java:147)
at com.aveksa.gui.pages.base.data.PageData.drawView(PageData.java:136)
at com.aveksa.gui.pages.base.data.PageData.handleRequest(PageData.java:122)
at com.aveksa.gui.pages.base.data.main.MainPageData.handleRequest(MainPageData.java:47)
at com.aveksa.gui.pages.admin.globalRole.detail.GlobalRoleBasePageData.handleRequest(GlobalRoleBasePageData.java:246)
at com.aveksa.gui.pages.admin.globalRole.detail.main.GlobalRoleMainPageData.handleRequest(GlobalRoleMainPageData.java:284)
at com.aveksa.gui.pages.PageManager.forwardRequest(PageManager.java:609)
at com.aveksa.gui.pages.PageManager.handleRequest(PageManager.java:409)
at com.aveksa.gui.pages.PageManager.handleRequest(PageManager.java:271)
at com.aveksa.gui.core.MainManager.handleRequest(MainManager.java:187)
at com.aveksa.gui.core.MainManager.doGet(MainManager.java:131)
Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment if you are on a WildFly cluster or a non-WildFly platform. The aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)
Cause
This is a known issue reported in engineering ticket ACM-104041.
For example,
- Create two Role Sets: Role Set RS1 and Role Set RS2 (Roles > Role Sets > Create Role Set > (RS1} and {RS2} > Next > Finish)
- Add Role R1 to Role Set RS1 and commit the changes. (Roles > Roles > Create/Discover > Create Role > {R1} > Existing Role Set: {RS1} > OK > Apply Changes > OK)
- Move Role R1 to Role Set RS2 without applying the changes. (Roles > Roles > {R1} > Edit > Existing Role Set: {RS2} > OK
- Delete Role Set RS1 (Roles > Role Sets > {RS1} > click on the trash can in the far right corner > OK)
- Revert the changes to Role R1 (Roles > Roles > {R1} > Revert Changes). The Revert Changes fails with the Request could not be handled error.
- Try to access Role R1. (Roles > Roles > {R1}) The Request could not be handled error occurs. The role is inaccessible.
Resolution
- RSA Identity Governance & Lifecycle 7.1.1 P07
- RSA Identity Governance & Lifecycle 7.2.0 P02
