On the last day of access, which process or task actually triggers the deprovisioning of a role with sunset date for a user?
During this deprovisioning, is an access request created, or does it happen automatically without a request?
Also, where in the system can we track or audit this role removal change?
When you place a request in Manage Access with Sunset dates then immediately a task gets created to remove same access from user once it gets provisioned.
During this deprovisioning, it happens automatically without a request.
The OOTB Audit for role sunrise/sunset is enabled by default. To check this, go to Advanced Analytics → Search Type: Audit → Select Action: Role Removed. Please check the screenshot below for the results.
@Narahari OOTB Scheduled Assignment doesn’t create new access request while doing sunset. Instead it calls Identity library for necessary compilation and validation and directly calls the Provision With Retries workflow to do the deprovisioning.
If you want to generate more specific audits, or create access request, you might want to modify this workflow by passing the plan to your LCM workflow. This should create an access request for you.
Note: Help the community by marking successful fixes as solutions. Feel free to react(, , etc.) with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.
There are two tasks which trigger the sunset and sunrise. One is the Perform Matians task and the second is Check Sunset Requests. The sunset and sunrise mechanism works on a and forget principle. To invoke these tasks, you should run these tasks.
Perform Matians task, (Sunraise)
Check Sunset Requests.
3rd question answer: You can check two places. One is the debug page, filtered with Request Object based on the days result expiration threshold. It will show when it is triggered and fired at sunrise and sunset. The second place is the Administrator Console > Provisioning Transactions.