Identity Invitation Attempting AD Provisioning Unexpectedly

:bangbang: Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.

Please consider addressing the following when creating your topic:

I have a Delimited File application configured as a source system along with an Identity Profile. This setup was working fine initially. Later, I configured Active Directory, and the delimited file aggregation continued to work without issues.

Recently, someone modified some configuration. Now, when I aggregate users from the Delimited File, identities are getting created successfully. However, during the Identity Invitation / Registration process, the system is attempting to create an Active Directory account.

Since Active Directory connectivity is currently not available, the identity registration process is failing.

I would like to understand:

Which configurations or settings could cause the invitation process to trigger AD account creation

What should be checked or reverted to ensure invitations do not attempt provisioning to Active Directory

Any guidance on the relevant configurations (Identity Profile, Lifecycle State, Provisioning Policies, Account Correlation, or AD settings) would be greatly appreciated.

What errors did you face (share screenshots)?

1 Like

Hi @narayanag,

Are there any birthright roles configured for your AD source or any access profile that is granted via lifecycle state?

2 Likes

Hi @narayanag ,
Have you checked the similar issue in Timeout waiting for response to message # from client error - Identity Security Cloud (ISC) / ISC Discussion and Questions - SailPoint Developer Community?
As per the solution from post 8, there was a problem with VA, which needed ccg to be deleted and VA restarted.

Other than that, it looks like you have some automatic provisioning either via lifecycle state configuration, or via birthright configuration as @UjjwalJain mentioned. If you didn’t encounter this error, you would’ve found out where acc provisioning comes from actually.