Hi.
We are having issues to provision all the attributes to Active Directory. The following are the warnings and errors we found from the search API (accountactivities).
“warnings”: [
“Account created but failed to modify : Failed to update attributes for identity “distinguishedName”. The requested operation did not satisfy one or more constraints associated with the class of the object.\n”
]
In the Account Requests, we notice the following warning and error:
“result”: {
“warnings”: [
“Account created but failed to modify : Failed to update attributes for identity “distinguishedName”. The requested operation did not satisfy one or more constraints associated with the class of the object.\n”
],
“errors”: [
“Account created but some attributes are not updated properly.”
],
“status”: “committed”
},
Hi Jo,
Thank you for your post. This errors comes when we are trying to set value which are not permitted at AD side. For eg middleName which is Initials has a limit for the number of characters we can send.
Could you please check on the above ? Also are you populating manager in the AD in the correct format ?
Hi @sjoyee , I believe the error is related to the character limit for one or more of the AD attributes that you are trying to provision while creating an AD account.
Refer AD documentation: All Attributes - Win32 apps | Microsoft Learn for character limit information and then compare it with your attribute values that you are sending from IDN to AD for the affected users. I think you will get the answer there.
Additionally, if you have pre-prod AD access, then you can try manually updating the attribute which you think might be causing the issue just to confirm.
Hi Rakesh. Thank you for the input! The error is the number of characters passed in the AD attribute to be provisioned. It works when we remove this attribute.
However, this attribute is needed for us to retrieve and put as value in the static field.
For example, distinguishedName = $abc,$bcd, but $bcd (retrieved from identity attribute) is having exceeding characters. Is there any way for us to filter out $bcd to be provisioned to AD, or other way to create a pattern using a combination of attribute in the plan and identity attribute?