Identity Process

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hello Experts,

Any idea how to run the process identity after our authoritative aggregation by automatically.

Thanks

2

Hi @niketnova ,

Processing Identity Data - SailPoint Identity Services check it.

if you want to perform identity processing use ISC REST APIs. sync-identity-profile | SailPoint Developer Community

3

Thanks for the document.

We are facing a challenge regarding the rehire use case.

We have an aggregation occurring at night, which altered the lifecycle status from terminated to active. Subsequently, it is required to calculate the username, but it is anticipating manual processing. Typically, we apply changes manually to recalculate the transforms; however, we are seeking a method to automate this process since it is in production, and we prefer not to handle it manually.

Additionally, could you assist me in configuring the process identity for all identities, as I am unable to locate any configuration steps?

4

Do you have workflows feature in your tenant.

5

As i am new in ISC. Yes we do have workflows feature enabled in our tenant.

Thanks

6

Okay, use below workflow json file to achieve yours case, in scheduled trigger provide time when you want to process identities of an identity profile.

in below add id and name under modifiedBy and Creator with your identity.
in DefinedVaribale operator identityProfileId modify with your identity profile ID.
in Http action, provide your tenant and clientId and clientSecret.

Test in sandbox, before migrating to production.

{
	"name": "Test-Identity Processing",
	"description": "Test",
	"modified": "2025-07-15T14:37:19.92630242Z",
	"modifiedBy": {
		"type": "IDENTITY",
		"id": "",
		"name": ""
	},
	"definition": {
		"start": "Define Variable",
		"steps": {
			"Define Variable": {
				"actionId": "sp:define-variable",
				"attributes": {
					"id": "sp:define-variable",
					"variables": [
						{
							"description": "This identity profile id used to process all the identities under the profile.",
							"name": "identityProfileId",
							"transforms": [],
							"variableA": "4dab30e7016846158d503759f875c28b"
						}
					]
				},
				"displayName": "",
				"nextStep": "HTTP Request",
				"type": "Mutation"
			},
			"End Step - Success": {
				"actionId": "sp:operator-success",
				"displayName": "",
				"type": "success"
			},
			"HTTP Request": {
				"actionId": "sp:http",
				"attributes": {
					"authenticationType": "OAuth",
					"method": "post",
					"oAuthClientId": "ndjhegu98bdewge2yj2bevxjndslkm",
					"oAuthClientSecret": "$.secrets.aa140926-c9f5-4569-9db1-cad2bbb7f9e5",
					"oAuthCredentialLocation": "oAuthInHeader",
					"oAuthTokenUrl": "https://bapu-sb.identitynow-demo.com/oauth/token",
					"requestHeaders": {
						"X-SailPoint-Experimental": "true"
					},
					"url": "https://bapu-sb.identitynow-demo.com/v2025/identity-profiles/{{$.defineVariable.identityProfileId}}/process-identities"
				},
				"description": "",
				"displayName": "",
				"nextStep": "End Step - Success",
				"type": "action",
				"versionNumber": 2
			}
		}
	},
	"creator": {
		"type": "IDENTITY",
		"id": "",
		"name": ""
	},
	"trigger": {
		"type": "SCHEDULED",
		"attributes": {
			"cronString": "0 0 * * *",
			"dailyTimes": [
				"1969-12-31T18:30:00.000Z"
			],
			"frequency": "daily",
			"id": "idn:cron-schedule",
			"timeZone": "Asia/Calcutta"
		}
	}
}
7

let me try. thanks for this.

8

hi @niketnova as @gogubapu mentioned you can definetly go with Workflow as one of the approach. SailPoint also provides another option for refreshing identities. You can use Time-Based Processing feature and configure nextProcessing identity attribute based on your need.