As of now in SailPoint IDN, we are able to raise access requests for Inactive Users as well.
Is there a way in which we can prevent Inactive users to be selected while raising the access requests? In short, we are looking to prevent access requests to be raised for Inactive Users in IDN.
I donât believe thereâs an OOTB option for this, but potentially possible via segmentation and or complex approval logic in Workflow.
There are some design decisions around inactive users to consider though:
What are the various scenarios for an identity to be âinactiveâ (i.e. terminated, leave of absence, etc.)?
Should âinactiveâ users of specific types (i.e. terminated) be excluded from IDN completely?
Can âAccess Requestâ be used to re-activate an identity? If so, then they need to be in the selection list.
Many times itâs a more complicated question of âWhat does âinactiveâ mean?â and based on the various scenarios itâs generally not all or nothing.
I have no idea if theyâll provide anything in the near, mid, or long term. Iâm not aware of anything currently, but Iâm also not a SailPoint employee
Is this the correct representation to filter the identities with Inactive lifecycle state?
The reason I am asking this question is, when I enabled the segment and perform testing, I noticed even for active users, I am unable to see the role that I have included in my segment.
As per my understanding, the segment will only apply to inactive users and the role which I have included in the segment shouldnât be visible in the request center for any of the inactive users.
Oh okay, thanks for the clarification @KevinHarrington , I am looking for a way in which recipients(in my case inactive users) shouldnât be made available in the request center so that no one can raise a request for these inactive users.
End goal is Inactive Users shouldnât be made available in the request center so that access request canât be submitted for them
Well, I believe apart from Segments (which rightly point out above by @KevinHarrington is only applicable to requestors), there are no other OOTB features currently available to restrict access requests being made for a defined set of identities (or recipients) in Request Center.
Forms is another new feature introduced in IDN but currently itâs not available for Request Center, but I heard it will be in some time. Once itâs available, you can customize the form as per your requirement.
You may explore another options like hosting a custom form in ServiceNow or any such product where you can customize it as per your needs but thatâs not a quick one, will take some good amount of efforts.
As Gaurav pointed out, this is not a current feature of segments and request center. There is an idea for this that you can comment on and vote for. https://ideas.sailpoint.com/ideas/GOV-I-2021