Click HERE to see how Saviynt Intelligence is transforming the industry. |
10/16/2024 07:42 AM
Hello,
We have configured the dependent application using endpoint filter which is working as expected when triggered the provisioning using technical rule.
But when we are requesting using ARS then new account task of child endpoint failing with below error:
Any suggestion here?
Regards,
Rahul
Solved! Go to Solution.
10/16/2024 07:43 AM
FYI...
We have child endpoint exposed in the ARS module as application.
Thanks!
10/16/2024 07:44 AM - edited 10/16/2024 07:45 AM
10/17/2024 12:42 AM - edited 10/17/2024 12:44 AM
Hello @rushikeshvartak ,
Thanks for the response as always Man.
I tried this option but its not working, I analyzed the logs and here what I found :
quartzScheduler_Worker-2-hnkhl","DEBUG","Add access task - <taskid> is found without accountkey, validating further...
ERROR","Call response: {"error":{"code":"Request_BadRequest","message":"A conflicting object with one or more of the specified property values is present in the directory.","details":[{"code":"ObjectConflict","message":"Another object with the same value for property proxyAddresses already exists.","target":"proxyAddresses"},{"code":"ObjectConflict","message":"Another object with the same value for property userPrincipalName already exists.","target":"userPrincipalName"},{"code":"ConflictingObjects","message":"A conflicting object with one or more of the specified property values is present in the directory.","target":"User_<id>"}],"innerError":{"date":"2024-10-17T07:30:03","request-id":"<rid>","client-request-id":"<cid>"}}}"
Error in provisioning: AccountID is mandatory
DEBUG","taskResult:: false
ecm-worker","azure.AzureADRestProvisioningService","quartzScheduler_Worker-5-hnkhl","ERROR","Error while creating account - <accountName> removing tasks from the list
Regards,
Rahul
10/17/2024 01:02 AM - edited 10/17/2024 01:02 AM
@rahul_p is the account name rule same?? In both the endpoints?
10/17/2024 09:10 AM
It seems a proxy address is already in use.
proxyAddresses Conflict:
userPrincipalName Conflict:
AccountID is mandatory:
Pre-validation Check: Use API calls to verify if userPrincipalName and proxyAddresses are unique before submitting a request. For example, use MS Graph API:
10/17/2024 01:16 AM
Hello @NM ,
Thanks for the response.
We have same account name rule and co-relation rule in both the endpoints.
Regards,
Rahul
10/18/2024 07:49 AM
Hello Everyone,
So the issue was with discrepancy of account name in account name rule, create JSON and account attributes.
Thanks all for your inputs.
Regards,
Rahul