Enhancement: Exclude Inactive Identities from Attribute Sync!

Description

:bangbang: SailPoint is excited to announce that Inactive (long-term) identities will be excluded from the attribute sync process! This enhancement is available in all sandbox tenants. It will begin rolling out to production tenants on October 7, 2024.

This enhancement was a top request following the initial release of New Capability: Management of Inactive Identities. Administrators will have more control over the the last update to leavers’ accounts, and see a reduction in unneeded provisioning load.

Problem

Attribute syncs to inactive identities’ accounts are unneeded in most cases. The extra traffic can cause infrastructure problems and interfere with leaver processes. 51 voters have asked us to solve this problem in this idea.

Solution

Inactive (long-term) identities will be excluded from the attribute sync process except when:

What’s the updated view of how the three identity states are used?

Active identities will be included in all services. Inactive (short-term) will be excluded from some services. Inactive (long-term) will be excluded from most services.

Area Active Inactive (short-term) Inactive (long-term)
Identity Picklists in Request Center :white_check_mark: Included :x: Excluded :x: Excluded
My Team UI for Managers :white_check_mark: Included :x: Excluded :x: Excluded
Scheduled Processing :white_check_mark: Included :white_check_mark: Included :x: Excluded
Apply Changes on Roles, Access Profiles, and Apps UIs :white_check_mark: Included :white_check_mark: Included :x: Excluded
Attribute Sync :white_check_mark: Included :white_check_mark: Included :x: Excluded
Apply Changes on Identity Profiles UI :white_check_mark: Included :white_check_mark: Included :white_check_mark: Included
Processing for Select Identities :white_check_mark: Included :white_check_mark: Included :white_check_mark: Included
Identity Attribution Promotion after Accounts Updated in Aggregations :white_check_mark: Included :white_check_mark: Included :white_check_mark: Included

What if I need to sync attributes for recent leavers?

You might require a recent leaver lifecycle state in addition to a long-term leaver lifecycle state if you need to sync attributes for recent leavers. For example, it’s common to see a two-stage termination step with lifecycle states named Terminated < 90 days and Terminated < 90 days. Identities in Terminated < 90 days would receive syncs because their lifecycle state is marked Inactive (short-term). Identities in Terminated > 90 days would not receive syncs because their lifecycle state is marked Inactive (long-term). Hold identities in the first-stage lifecycle state as long as you’re required to sync attributes.

Lifecycle states
Pre-Hire Active
Active Active
Leave of Absence Active
Terminated < 90 days Inactive (short-term)
Terminated < 90 days Inactive (long-term)

What if I need to sync attributes for long-term leavers?

To continue the previous example, you might need to sync attributes for identities in the second-stage lifecycle state (Terminated < 90 days). In this scenario, the administrator can use the Synchronize Attributes action. Synchronize Attributes can also be called via /beta/identities/:identityId/synchronize-attributes.

Will attributes sync when an identity just became a long-term leaver?

The system will complete one last attribute sync when an identity enters a lifecycle state that is configured as Inactive (long-term). This covers most use cases concerning OU moves, deletions, etc. specified in a Before Provisioning rule.

Who is affected?

All customers who have implemented both identity states and attribute sync.

Action Required

Review and implement the Identity States feature if you haven’t yet. The Identity States feature enables you to mark identities as inactive to exclude them from access requests, manager views, and more. This enhancement adds one more reason to enable the Identity State feature. A guide to enable the feature is available here: New Capability: Management of Inactive Identities.

Important Dates

  • Sandbox: Monday, September 30th
  • Production: The week of Monday, October 7th

Additional Resources

New Capability: Management of Inactive Identities

5 Likes

Will there be the ability to turn it on for all statuses for a specific source? We have scenarios were some security attributes have to be changed after a termination to an account that can’t be deleted and is only disabled. I’m curious if we are going to have to start working a daily report to catch ones that didn’t get updated during the “one last chance” run.

Wait? Really? This is a thing? please do not do this in the way you have it documented. This should be configurable. We literally just went live with AD provisioning and attribute sync and the timing of this is not good. Also, why not allow the customer to choose rather than make this decision based on 51 customers?
DOWN VOTE!!!

Also, if this went live in Sandbox Sept 30, why am i just getting the notice in the UI yesterday? C’mon SailPoint! do better!

Hi Jill,

I added a bit more context to the announcement explaining the configuration options that are available here. There are a couple ways to ensure those “last syncs” happen as desired.

We agree. The posts are supposed to be timed with when the item goes to sandbox. We had some trouble with the automation on this. The in-app notice did go out on time. Sorry about that.

Hi Kirk,

We’ll get a meeting scheduled with you early next week. Joel will be in touch with details.

Agree that this should be configurable, stop forcing us into changes that could easily fit everyone’s needs if we just had options rather than “that’s just how it is now”. The idea is great and I very much see why the change was made, but please never get rid of our options in the process.

Hi Benjamin,

Thanks for this. We did have to strike a balance here, and we did consult a good number of customers in the process of designing this. I added a bit more context to the announcement explaining the configuration options that are available here.

1 Like

I am not seeing a “last” attribute sync when the lifecycle changes to terminated and I am also not seeing the API attribute sync working either in our sandbox

Hi Austin,

We did fix a bug where syncs were being blocked for inactive_long_term identities when using either Synchronize Attributes button or this endpoint. The fix was deployed yesterday. Could you try that again, please?

Could you give me a quick bulleted list of how your “last” attribute sync use case is working?

It is not working. Ive tried via API and changing lifecycle states.

The change shouldn’t affect how the lifecycle state calculation works for inactive identities should it?

Hi @ryanyamayama ,

No, it would not. Identity State and Lifecycle State are two separate attributes. The Identity State is of course determined by the Lifecycle State.