CreateChangeRequest webservice call with <AccountChange> does not fail on SoD Violations for RSA Via Lifecycle & Governance
Originally Published: 2016-07-14
Last Modified: 2023-10-06
Article Number
Applies To
RSA Version/Condition: 7.0
Issue
Given the SoD rule with the Entitlement Specification as noted below, a user having or requesting both the Role Administrator and System Administrator roles should result in an SoD violation.
Now, if a user named 'jsmith' who already has the Role Administrator role requests the System Administrator role using the request xml below through Webservices, the Change Request gets created successfully instead of showing SoD violation details.
The webservice call is shown here:
<Changes> <AccountChange> <Operation>Add</Operation> <User>jsmith</User> <BusinessSource>Aveksa</BusinessSource> <ApplicationRole>System Administrator</ApplicationRole> </AccountChange> </Changes>
The code below shows the wrong response:
<createChangeRequest>
<Request type="fulfillment">
<Id>51</Id>
<Name>00091</Name>
</Request>
</createChangeRequest>Resolution
The correct webservice request xml is shown here, that should be sent for user 'jsmith' in the above example.
The webservice call is shown here:
<Changes> <UserChange> <Operation>Add</Operation> <User>jsmith</User> <BusinessSource>Aveksa</BusinessSource> <ApplicationRole>System Administrator</ApplicationRole> </UserChange> </Changes>
The correct response is shown here, now with violation details. The EntitledId value refers to the internal database ID of the user.
<Request> <Violations> <Violation> <AccountId/> <ActionName/> <ApplicationId>1</ApplicationId> <ApplicationName>Aveksa</ApplicationName> <CollectorId/> <DetectionDate/> <EntitledId>14</EntitledId> <EntitlementId>358</EntitlementId> <EntitlementName>System Administrator</EntitlementName> <EntitlementType>app-role</EntitlementType> <FirstName>Dan</FirstName> <Id>0</Id> <IsDirect>1</IsDirect> <LastName>Smith</LastName> <Path/> <ResourceName/> <RuleName>SOD Rule</RuleName> <State>CE</State> <UserDisplayName>Smith, John</UserDisplayName> <ViolatingEntId>358</ViolatingEntId> <ViolatingEntName>System Administrator</ViolatingEntName> <ViolatingEntType>app-role</ViolatingEntType> </Violation> </Violations> </Request>
Related Articles
BlackBerry browser get stuck on javascript collector 19Number of Views Creating change request using parameter <scope> via webservice call in RSA Identity Governance & Lifecycle 31Number of Views createChangeRequest Delete Account web serivce call not working in RSA Identity Management and Governance 6.9.1 43Number of Views If the RSA Identity Governance and Lifecycle Rule Status is invalid, a Segregation of Duties (SOD) rule definition takes … 51Number of Views "The request could not be handled" message occurs in the RSA Identity Governance & Lifecycle UI when a rule remediator is … 66Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?