I have a request to preserve CUCM end user accounts whenever they transition from Active LDAP Users to Inactive LDAP Users. The end user accounts will frequently be disabled in AD, but the users come back shortly afterward and so all the associations for the CUCM end user account need to be reconfigured. The plan that I have to accomplish this is to
1. Check periodically via AXL for the inactive LDAP accounts
2. Call the executeSqlUpdate method to change the user status to "1" (active)
3. Call updateUser->convertUser to move them to a local account
When the user account is re-activated in AD, they will transition back to an active LDAP user.
The question that I have is around the executeSqlUpdate call. The updateUser request doesn't allow us to modify the status attribute of the user, so I'm wondering if there is some negative impact of using SQL to flip the status value of the end user account, or would it be safe to do this assuming all the necessary precautions are taken when calling the executeSqlUpdate method?
Thank you
