...
After the change the modification can be verified with the following request. For the user password verification only the plain password is needed to pass in the body of the POST request.
Code Block |
---|
POST https://VFC_MR_DOMAIN//verba/restapi/v1/users/16/password/verify new plain password |
...
The following example shows how to change the login name and the password for an LDAP server in the same request. The password has to be in plain format.
Request
Code Block | ||
---|---|---|
| ||
PATCH https://VFC_MR_DOMAIN/verba/restapi/v1/adSyncProfiles/13F72189-2EEB-425F-885B-7D1BBA83DDEB
Content-Type: application/json
{
"userName": "john.doe",
"ldapPassword": "new plain password"
} |
Response
Code Block |
---|
{
"host": "ldap host",
"port": 1234,
"userName": "john.doe",
"id": "13F72189-2EEB-425F-885B-7D1BBA83DDEB",
"description": "ldap description enabled",
"enabled": true,
"type": "ldap"
} |
The non sensitive data change can be validated with the previous response, which contains the whole entity object with the new modified values. The sensitive information can be verified with the following request. Due to an AD Synchronization Profile entities can have different types with different object properties, for the password verification the verified property name has to be passed too with the known plain password.
Code Block |
---|
POST /verba/restapi/v1/adSyncProfiles/13F72189-2EEB-425F-885B-7D1BBA83DDEB/password/verify
{
"property": "ldapPassword",
"value": "new plain password"
} |
...