Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

ENABLEACCOUNTJSON is not enabling account in OpenLDAP

Caesrob
Regular Contributor
Regular Contributor

Hello,

We are using the ENABLEACCOUNTJSON to enable a disabled account through user update rules.

The Enable account task is created, but when we try to provision the task fails. There are no errors in the provisioning comments, but we do get this error in our logs:

Caesrob_0-1686235067287.png

We do not use objectGUID as reconcilation field, but we do use another field (entryDN) which is also always unique. 

Can anyone help us with this error? Find current ENABLEACCOUNTJSON below:

{
"DISABLEACCOUNTCHECKRULE":[ "CN=${user.customproperty1},ou=STUDENT,o=uhasselt,c=be"],
"USEDNFROMACCOUNT": "YES",
"pwdLockout" : "FALSE",
"pwdPolicySubentry" : ''
}

We have also tried:

{
"DISABLEACCOUNTCHECKRULE":[ "CN=${user.customproperty1},ou=STUDENT,o=uhasselt,c=be"],
"USEDNFROMACCOUNT": "YES",
"AFTERENABLEACTIONS":
"{pwdLockout : FALSE, pwdPolicySubentry : ''}"
}

PS: Full logs added in attachments.

4 REPLIES 4

SB
Saviynt Employee
Saviynt Employee

Based on the error and the recommendation, we do need to use objectGUID  in reconciliation field.  Can you update the same and then try once.


Regards,
Sahil

Caesrob
Regular Contributor
Regular Contributor

objectGUID is not an attribute in our OpenLDAP. We are using entryDN as reconcilation field, which is also a unique identifier.

SB
Saviynt Employee
Saviynt Employee

can you run the job for only 1 task (Create a new one) and share the logs with the exception you are getting.


Regards,
Sahil

SB
Saviynt Employee
Saviynt Employee

If it is still not working, can you run the job for only 1 task (Create a new one) and share the logs with the exception you are getting.


Regards,
Sahil