Accounts created from an RSA Via Lifecycle and Governance account template are not removed from UI when request item is rejected or cancelled
Originally Published: 2016-12-05
Article Number
Applies To
RSA Version/Condition: 6.9.1, 7.0.0
Issue
When an account template is associated to an application and Entitlements require account is enabled, the new account creation triggers automatically for the request created to add entitlements. If the request item to create an account is rejected in the approval phase or cancelled in the fulfillment phase, the account should be removed from the UI. However this is not happening.
Issue 1: Issue when items are rejected in approval phase
- The Simple Account template is created and associated to an application and enabled Entitlements require account.
- The request is created to add entitlements to multiple users for the account template associated application. That approval is rejected for one of the users and accepted for another user:
- Since the create account for salva was rejected, we accept this account to not be created in the application. Only the account krao is to be created. When we go into application we can see account salva was created.
- The account for salva shows as local user mapping:
Issue 2: Issue when items are cancelled in fulfillment phase
- A request is created to add entitlements to two other users. In the request, items are accepted in approval phase. Items are cancelled for one user in fulfillment phase:
- In the application we could see the cancelled account is created as well:
Resolution
- For 6.9.1 update to 6.9.1P18 or 6.9.1 P19 to get the fix
- For 7.0.0 or later, upgrade to 7.0.1 P01 or 7.0.1 P02
Workaround
Before running the script, do the following:
- Take a full backup of AVUSER schema (that is, the whole RSA Via Lifecycle and Governance database).
- Within the DeleteStaleCreateAccount script is the following SELECT statement. Run just this statement to find the list of accounts that are going to be deleted, and make sure it does not contain anything we need to preserve in the database.
SELECT operand_name AS account_name, operand_id AS oid
FROM t_av_change_request_details crds
WHERE crds.operand_type = 'AC'
AND crds.full_operation = 'CreateAccount'
AND crds.state in ('RJ', 'CA')
AND NOT exists (-- Exclude accounts that had not been completely rejected
SELECT 1 FROM t_av_change_request_details cri
WHERE ((cri.operand_type = 'AC' AND cri.operand_id = crds.operand_id)
OR
(cri.value_type = 'AC' AND cri.value_id = crds.operand_id))
AND cri.state NOT IN ('RJ', 'CA'))
AND NOT exists (-- Exclude collected accounts
SELECT 1 FROM t_av_accounts acc
where acc.id = crds.operand_id
AND acc.adc_id > 0) ;
- Make sure that accounts we want to delete are listed by the above query.
- Then execute the SQL script.
Attachments
If the attachment does not open when clicked, please refresh the page and try again. You must be logged into view the file(s).
Related Articles
How to view workflow variable values during workflow execution in RSA Identity Governance & Lifecycle 130Number of Views RSA Governance & Lifecycle Recipes: Risk Analytics Dashboard 41Number of Views RSA Identity Governance and Lifecycle - 702 Migration fails with 'ORA-02260: table can have only one primary key' 44Number of Views Provisioning-Termination Rule fails to filter on Custom Attributes that have the same Display Names across Multiple Object… 158Number of Views Migration from 7.0.1 to 7.0.2 fails with error PLS-00323: subprogram or cursor 'PROCESS_ACTIVE_USER_ACC_MAPS' is declared … 15Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?