# Identity Processing -

**URL:** <https://developer.sailpoint.com/discuss/t/identity-processing/175481>\
**Category:** SHF Discussion and Questions\
**Tags:** sailpoint-identity-security\
**Created:** [September 2, 2025, 4:57am UTC](https://developer.sailpoint.com/discuss/t/identity-processing/175481 "2025-09-02T04:57:00Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gopi2000](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/gopi2000/32/21706_2.png) [@Gopi2000](https://developer.sailpoint.com/discuss/u/Gopi2000)\
**Post date:** [September 2, 2025, 4:57am UTC](https://developer.sailpoint.com/discuss/t/identity-processing/175481/1 "2025-09-02T04:57:00Z")

</div>

Hi Folks, I need to process all my identities coming from my auth source (2000+ accounts). Since there is no change in the identity profile, the ‘Apply Changes’ button is not workable. I also should not use the API to refresh. Could you please suggest a way to process these identities?

---

<div class="post-metadata">

**Author:** ![amishra97](https://avatars.discourse-cdn.com/v4/letter/a/50afbb/32.png) [@amishra97](https://developer.sailpoint.com/discuss/u/amishra97)\
**Post date:** [September 2, 2025, 6:27am UTC](https://developer.sailpoint.com/discuss/t/identity-processing/175481/2 "2025-09-02T06:27:42Z")

</div>

@Gopi2000 I would have changed the mapping for the least significant identity attribute and restored it to its initial state.

For example, suppose that the postal code of the Auth source is linked to the identity attribute _zipCode_.I would have changed the mapping of _zipCode_ to a random property and then back to _postalCode_.The apply changes button would appear in the upper right corner in this manner.

---

<div class="post-metadata">

**Author:** ![schattopadhy](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/schattopadhy/32/8854_2.png) [@schattopadhy](https://developer.sailpoint.com/discuss/u/schattopadhy)\
**Post date:** [September 2, 2025, 10:12am UTC](https://developer.sailpoint.com/discuss/t/identity-processing/175481/3 "2025-09-02T10:12:22Z")

</div>

> [@Gopi2000](#):
>
> rocess all my identities coming from my auth source (2000+ accounts). Since there is no change in the identity profile, the ‘Apply Changes

@Gopi2000 you can try to modify any attribute of less importance in the profile it will again come

---

<div class="post-metadata">

**Author:** ![Gopi2000](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/gopi2000/32/21706_2.png) [@Gopi2000](https://developer.sailpoint.com/discuss/u/Gopi2000)\
**Post date:** [September 2, 2025, 10:19am UTC](https://developer.sailpoint.com/discuss/t/identity-processing/175481/4 "2025-09-02T10:19:52Z")

</div>

@amishra97 @schattopadhy Is there any possibility without touching Identity Profile

---

<div class="post-metadata">

**Author:** ![amishra97](https://avatars.discourse-cdn.com/v4/letter/a/50afbb/32.png) [@amishra97](https://developer.sailpoint.com/discuss/u/amishra97)\
**Post date:** [September 2, 2025, 11:22am UTC](https://developer.sailpoint.com/discuss/t/identity-processing/175481/5 "2025-09-02T11:22:16Z")

</div>

@Gopi2000 You can run unoptimized aggregation for the auth source.

[Account aggregation](https://developer.sailpoint.com/docs/api/beta/import-accounts/)

---

<div class="post-metadata">

**Author:** ![suresh4iam](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/suresh4iam/32/29513_2.png) [@suresh4iam](https://developer.sailpoint.com/discuss/u/suresh4iam)\
**Post date:** [September 2, 2025, 9:15pm UTC](https://developer.sailpoint.com/discuss/t/identity-processing/175481/6 "2025-09-02T21:15:56Z")

</div>

Run the unoptimized aggregation of Auth source by using VS Code ISC plugin. Anyway it uses API internally. Otherwise I don’t see any other option to process all identities in an identity profile without touching it and without using API.

---

<div class="post-metadata">

**Author:** ![sauvee](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sauvee/32/23601_2.png) [@sauvee](https://developer.sailpoint.com/discuss/u/sauvee)\
**Post date:** [September 3, 2025, 11:48am UTC](https://developer.sailpoint.com/discuss/t/identity-processing/175481/7 "2025-09-03T11:48:35Z")

</div>

The best option (in my opinion) is to run the ‘Process Identities under Identity Profile’ API endpoint: /v2025/identity-profiles/:identity-profile-id/process-identities

> **[sync-identity-profile | SailPoint Developer Community](https://developer.sailpoint.com/docs/api/v2025/sync-identity-profile)**
>
> The SailPoint Developer Community has everything you need to build, extend, and automate scalable identity solutions.

---

<div class="post-metadata">

**Author:** ![udayputta](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/udayputta/32/14195_2.png) [@udayputta](https://developer.sailpoint.com/discuss/u/udayputta)\
**Post date:** [September 3, 2025, 7:12pm UTC](https://developer.sailpoint.com/discuss/t/identity-processing/175481/8 "2025-09-03T19:12:43Z")

</div>

hi @Gopi2000 ,

One way to do the automated processing for your identities coming from auth source is by configuring nextprocessing identity attribute. This will process the identity at the specified time. So, based on your use case you may configure the time when you want to run identity processing. Here is the complete details about this Time Based processing.

> **[Processing Identity Data - SailPoint Identity Services](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html#time-based-processing)**
>
> SailPoint Identity Services Documentation

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [November 2, 2025, 7:12pm UTC](https://developer.sailpoint.com/discuss/t/identity-processing/175481/9 "2025-11-02T19:12:54Z")

</div>

Closed on November 2, 2025, 7:12pm UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
