Accounts created from Change requests that have not been fully submitted in RSA Identity Governance and Lifecycle
Originally Published: 2016-11-21
Article Number
Applies To
Issue
Below is the Account template with pending account parameter.
It is associated to an application with "Entitlements Require Account" setting enabled.
Create a change requests explicitly to add any entitlement to the users for the application with account template associated. Navigate through all the pages. On the last page of the change request (which has Finish button). Do NOT click finish to submit the change request, instead click cancel.
Go back to the application and in the accounts tab you will see the account created.
Resolution
Related Articles
Xudad crashes when a certificate request is submitted via OneStep 5Number of Views This request contains no changes. It cannot be submitted error when adding entitlement belonging to a role in RSA Identity… 24Number of Views A Business Role Request with an existing unsuccessful Pending Submission Request that creates a Pending Account can still … 52Number of Views In RSA Identity Governance & Lifecycle the warning 'No CSRF guard token was found in the submitted request' is encountered… 133Number of Views RSA SecurID On-Demand Authentication (ODA) requires submitting the token within two minutes or 120 seconds after the PIN i… 147Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Release Notes (January 2026) Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU Disabling weak ciphers using port 1813 in RSA Authentication Manager 8.3 patch 1
Don't see what you're looking for?