AD Connector as Target

Hi All,

Question : I am trying to do Provisioning in my source i.e., Active Directory. Accounts are getting created in AD but all the attributes are not populating in AD end.

For example : I am sending “displayName” value via Create Account page but while doing provisioning it is failing. Value are not getting stored in AD .

But when I trying to do so directly in AD with same Service Account I am able to update its display name.

Kindly help with the issue.

The directory service cannot perform the requested operation on the RDN attribute of an object.

Hi,
Can you please share the Account Activity for the user ?

Attributes after cn, like eduPersonAffiliation and others are not present in Account Schema.

How even they are getting populated there?

They would be coming from the Create Account if you have added them. So if you want to remove them you can remove it.

they are not present in Create Account page:(

Any suggestion on this, as the red sign besides the attributes are those which is not getting populated in AD end

@RAKRHEEM Please find the Account Activity Screenshot

HI @RAkhauri ,

We don’t see the screenshot attached. Could you please attach it again?

Hi @RAkhauri ,

as mentioned by @RAKRHEEM above please check the account activity in search tab if all the attributes are populating correctly as provided in the create account, check if any of the attribute format is not correct for ex: manager dn or expiredate, try providing static values in create account and test creating account

If your base account creation is not showing AD after provisioning and there are attribute errors, look in the Provisioning Settings area of the source configuration.

Make sure that “Rollback Partially Created Account” is NOT checked.

I would also verify the createAccount profile using the API.

get-provisioning-policy | SailPoint Developer Community

Hi @rkhade ,
Thanks for writing up here.

I have tried in that manner too by providing static input in displayname, sn to check whether it is updating or not but still it is throwing same error.

Also I have reinstalled the IQ service too. Do we have to provide the IQ Service Password again in AD Connector if we have reinstalled it.

Here it is:


Test Connection and account aggregation will work without IQService. Can you cross check if all the connection details given are correct? Hope there are no changes made to Service account perms.

Also, I would suggest enabling logging and check the logs for more info.

Account creation is working fine but it is failing to add or modify some attributes, try creating account only with mandatory attributes and check if those attributes are populating correctly, once the account is created, keep adding attributes one by one and test account creation then you will come to know which attribute is causing the issue.

in my case it was manager DN can you check that also.

Also can you upload the full screenshot of account activity, which will show the attributes and values.

Hi

If any attributes got failed to add or update the remaining attributes also not update in the target. The actual attribute which causing issue it breaks other attributes as well. So check one by one the exact attribute which causing the failure.

Best Regards,
Siva.K

Thanks Everyone, It worked.

But new error is coming up now and test connection is failing.

here is the error screenshot :

Source is Active Directory,

IQ Service Port : 6060
TLS is checked.
For client Authentication, Account is having Domain User Account.

TimeOut set on IQ Service is 15 secs.

Add increase time in the source connection path
Ref
https://documentation.sailpoint.com/connectors/active_directory/help/common/identitynow_topics/timeout_errors.html

1 Like

It is failing , 400 Bad Request
<
[
{
“op”: “replace”,
“path”: “/connectorAttributes/timeout”,
“value”: 60
}
]
/>

If you are first time adding you should you add instead of replace.

Try with op is add

1 Like