Hi
Firstly ensure the Identity Attribute is set to distinguishedName in the Account Schema of your AD application in IdentityIQ
Also try to Validate all attributes you’re provisioning for length, existence in AD, and correct formatting.
Thank you, it already like that and even the attribute length validated, no issue at all i am not sure what is wrong
Okay Check Your IQService whether its upto date
Also check your ProvisioningPlan maybe it sends an empty string where IQService expects a value.
Or if possible share here the plan
Yes actually it works now when i re login again to the SailPoint and i figure out the user what already in Active directory with the same entitelment that why it was rejecting, i tried new user from HR source to add to active directory with new provisioning and it works now
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
