What are watches in RSA Identity Governance & Lifecycle
Originally Published: 2014-10-22
Last Modified: 2023-10-06
Article Number
Applies To
RSA Version/Condition: 7.0.x, 7.1.x, 7.2.x
Issue
Resolution
For example, when an entitlement is provisioned to a user or revoked from a user whether manually or via AFX, a watch is opened for that change request activity so that the next collection can verify if the entitlement was actually provisioned or revoked. The change request itself goes into a pending verification state. The next collection verifies or watches whether or not the activity took place. If the entitlement has been successfully provisioned or revoked, the open watch is closed and the loop is complete. If the collection is unable to verify if the activity took place, the watch remains open and the change request remains in a pending verification state.
Related Articles
G&L Email Delivery Fails with ORA-01407: Cannot Update T_EMAIL_LOG to NULL Number of Views How to close ports used by the RSA Authentication Agent to block SSLv3 communication to RSA Authentication Manager 8.x Number of Views In RSA Identity Governance & Lifecycle, what is the difference between an account's Last Collected Date and Last Collected… Number of Views Generate a report of users with more than one token assigned in RSA Authentication Manager 8.x Number of Views What are the custom attribute data type limits in RSA Identity Governance & Lifecycle Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager Patch Updates RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Authentication Manager Supported Hardware and Upgrade Paths Troubleshooting AFX Connector issues in RSA Identity Governance & Lifecycle
Don't see what you're looking for?
