DMS API: Bad password count being updated.

Document ID : KB000024006
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue/Problem/Symptoms: 

Using DMS API in Java and doing User Change Password. User does not get disabled after the maximum incorrect passwords allowed by the Password Policy. Bad password count is being updated in the User Directory (AD) attribute.

 

Environment:  

All versions of SDK, DMS API.

Cause: 

Non-admin user should be used to initialize the DMS API and call the login() method.

Resolution/Workaround:

This would require to use a non-admin user to do a login() method call and use that to initialize the DMS API, instead of the admin user and password. So basically, in the login () call you would use an end user's id/password instead of the admin user id/password. The example is the sample DMSApiSample.java that comes with SDK installation.

 

Additional Information:

N/A