Creating Service Accounts for SailPoint API Automations

Description

Service accounts are identities in Identity Security Cloud (ISC) that aren’t real people. Their purpose is to provide credentials for automation services that can be managed and controlled separately from real identities. As a developer of integrations with ISC, there are two main advantages of creating service accounts: you can scope access to the least privilege necessary to do the job, and you can ensure that your integration’s access doesn’t end when you leave your organization. If you use your user account to generate credentials for integrations, they are tied to your level of access (i.e. admin) and can be revoked when you leave the organization - this could cause downtime in your integrations. Join Christina Gagnon as she demonstrates how to create and manage service accounts in ISC.

Additional Resources

6 Likes

@christina_gagnon i am having issues getting this to work. We use Entra ID to authenticate for our normal accounts for access to ISC. I am able to get through all of this but as soon as i grant one of the service accounts helpdesk user level i am being forced to set up MFA. Then on login after the MFA process it directing back to Entra login which the flat file account doesn’t have.

Am i doing something wrong or do we have something set up incorrectly?

@swcoleman

Try adding ?prompt=true to the login URL:

https://tenantname.identitynow.com/login/login?prompt=true

This should bypass the identity provider. You can find more details here:

1 Like

That’s where I am starting. I enter credentials then i get prompted for MFA. After the MFA it’s winding back up at Microsoft authentication. If i go back to https://tenantname.identitynow.com/login/login?prompt=true again and log in seems to let me in. thanks for the help.

2 Likes

Agree . ISC should have some easy way for managing the API within the workflow

Created idea for similar requirement
https://ideas.sailpoint.com/ideas/GOV-I-4006

1 Like