Hi Everyone,
We have integrated Azure Active Directory source in IdentityNow and the objectId is considered as AccountID and userPrincipalName as AccountName as per the schema.
While creating the user account in Azure AD from IdentityNow, we are not sending objectId in the create profile and IdentityNow is auto-generating the objectId while creating the account.
Randomly I see the issue with creation of account which is :
[“sailpoint.connector.ConnectorException: Exception occurred. Error message - HTTP not ended OK. Response Code - 400 Error - A password must be specified to create a new user.”]
This error is very random while creation of users and we are sending password in create profile using “Create Password” Generator. Our observation with success and failure scenarios from provisioning activities is that - In failure cases, we dont see the objectId being generated and added as the nativeIdentity. In success cases, we can see the objectId being generated and added as nativeIdentity to the plan.
Any insights for this random issue?
Thanks,
Archana