- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Request struck in pending Verification
Request getting Struck in Wait for Verification.Please tell how to know what the issue is
- Tags:
- Community Thread
- Discussion
- Forum Thread
- Identity G&L
- Identity Governance & Lifecycle
- IG&L
- IGL
- RSA Identity
- RSA Identity G&L
- RSA Identity Governance & Lifecycle
- RSA Identity Governance and Lifecycle
- RSA IGL
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi,
Apologies if you already know this, but the Pending Verification step means the changes have been marked as Complete (either manually or by AFX) and is now awaiting collection from the target system to verify that the changes have been made.
The reason the request only get marked as Completed once it's been verified against the target system is because although the change is marked as Complete, it may not actually of been successful, for example, an administrator could mark the request as complete but not actually perform the correct action. We refer to this as the closed loop process.
Have you run the associated collector to verify that the changes have actually been made? Have you checked the target system to confirm the changes have been made?
Thanks,
Clive
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi,
Apologies if you already know this, but the Pending Verification step means the changes have been marked as Complete (either manually or by AFX) and is now awaiting collection from the target system to verify that the changes have been made.
The reason the request only get marked as Completed once it's been verified against the target system is because although the change is marked as Complete, it may not actually of been successful, for example, an administrator could mark the request as complete but not actually perform the correct action. We refer to this as the closed loop process.
Have you run the associated collector to verify that the changes have actually been made? Have you checked the target system to confirm the changes have been made?
Thanks,
Clive
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Most of the time these requests are the result of a design problem. The customer does not want to fix the problem (design) they want to fix the consequences of the design.
As Clive noted the intention of the verification is to confirm that the (correct) items was actually created by AFX.
The most common problem is when AFX creates the (correct) item but the collection is not setup correctly to collect it. The failure appears to occur at AFX so this is typically where customers look for an issue, but most often the issue is actually at the collector.
For example:
- The simplest use case is where the correct item to create is item A, and item A is created and item A is collected.
- The use case that verification is designed to identify as an error is where the correct item to create is item A but item B is created in error and item A is not collected.
- But the most common failure is where the correct item to create is item A, and item A is created, but item B is collected.
Always make sure that the item that you create in AFX can actually be collected.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi
Thanks the information .
No I haven't run the associated collector to verify that the changes have actually been made or not.
But when i checked in user profile the requested access of this particular request had been added to user profile.
Thanks
Vinita Singh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi
Thanks for information , This is really very helpful
Thanks
Vinita Singh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Have you since run the collector?
If yes, is the request now marked as Completed?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Instead of running the collector, I mannually completed the Workflow of the request and request moved to completed state
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Out of interest, is there any particular reason why you didn't run the collector?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
As those Entitlement application name is been changed by some anaylsts , so running the collectors will not have any effect and as access is been added to user so I just moved the request to completed state manually.
Is this not an appropriate way,Please advise.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
As a one of activity I don't see any issues.
Going forward you obviously want your requests to complete automatically once collection has successfully occured.
