000036069 - "The request could not be handled" message occurs in the RSA Identity Governance & Lifecycle UI when a rule remediator is set to a deleted user

Document created by RSA Customer Support Employee on Mar 20, 2018
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000036069
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.0.1, 7.0.2
 
IssueThe following error occurs in the UI when the rule remediator is set to a deleted user. 
 
The request could not be handled

 

User-added image
 


If a Segregation of Duties (SoD) rule or User Access rule that has been assigned to specific remediator ID and this remediator is then deleted in the Identity Data Collector (IDC) endpoint, when clicking on Rules > Violations then clicking on the open violation.


The same error also happens if you try to edit the rule definition under Rules > Definition and click on the rule name then click on the General tab:
 
User-added image


The following error is seen in the /home/oracle/wildfly8.2.0.Final/standalone/log/aveksaServer.log


ERROR (default task-10) [com.aveksa.gui.core.MainManager]
java.lang.RuntimeException: java.lang.NullPointerException
at com.aveksa.gui.objects.rule.GuiSODRuleDefinition.<init>(GuiSODRuleDefinition.java:78)
at com.aveksa.gui.pages.rule.detail.RuleDetailHelper.getUserConditionHtml(RuleDetailHelper.java:903)
at com.aveksa.gui.pages.rule.detail.RuleDetailHelper.printCondition(RuleDetailHelper.java:136)
at com.aveksa.gui.pages.rule.detail.RuleDetailHelper.printContent(RuleDetailHelper.java:114)
at com.aveksa.gui.pages.other.detailpopup.DetailHelper.printContent(DetailHelper.java:66)
at com.aveksa.gui.pages.other.detailpopup.DetailHelper.printContent(DetailHelper.java:62)
at com.aveksa.gui.pages.rule.detail.main.RuleDetailMainPageView.printContent(RuleDetailMainPageView.java:60)
CauseThis is failing because of NullPointerException error when trying to create a user object. If the rule remediator was deleted then a null pointer was generated because the search for the user filter did not include deleted users.
ResolutionThis bug is fixed in 7.0.2 P04. Deploy the patch to correct the issue.

Attachments

    Outcomes