For your “remove access” step, doesn’t this need to be handled in a loop? My understanding is that remove access requests can only be submitted one at a time, so if a user has more than one access item, it will fail if not done in a loop.
thanks for this post as it is very timely to something I am currently working on for Emergency Terminations. I would like to use the option 2 in your post by manually updating the lifecycle state on an identity. The challenge I am facing is that I think only Admins can modify the Identity Lifecycle State yet in my company, tier 3 IT support performs the emergency terminations. Do you know of a way to allow Helpdesk User Levels to update Identity Lifecycle State manually?
Thanks
Unfortunately Sailpoint doesn’t support updating lifecycle states using helpdesk user level, they will need Admin access to be able to switch states manually.
Hello @sharvari , We are looking to implement the Emergency terminations using the workflow. We are trying to invoke the API from Workday business process. Do you happen to have any insight on how this can be setup on Workday side.
I am not very familiar with how this needs to be setup on workday side but here’s the information you need to share with them so they can make the call to workflow.
How can we add steps to workflow like
once we get a heads up from HR system to SailPoint
employeeStatusCode as T or terminated then
disable AD and OKTA then
Kill AD an OKTa sessions then
move the user account to disable OU
sync to downstream systems
reset password then
hide From GAL
remove Distribution list
remove user from all cloud groups
convert to mailbox to shared mail
give manger delgate access
delete calendar events
we want to move away from Powershell script to Workflows fully ? how can we do achieve this ? if someone have already build it ? share a similar workflow
It may be best to create a separate post in the forum for this question, so it has more visibility.
A lot of these tasks that you mentioned can be achieved directly via OOB functionalities and do not require a workflow. You can use the Lifecycle states to trigger disables etc and do an AfterModify rule for some of the other AD tasks.