...
| Code Block |
|---|
{
"host": "ldap host",
"port": 1234,
"userName": "john.doe",
"id": "13F72189-2EEB-425F-885B-7D1BBA83DDEB",
"description": "ldapLDAP AD Synchronization Profile 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 checked plain password.
| Code Block |
|---|
POST https://VFC_MR_DOMAIN/verba/restapi/v1/adSyncProfiles/13F72189-2EEB-425F-885B-7D1BBA83DDEB/password/verify
Content-Type: application/json
Accept: application/json
{
"property": "ldapPassword",
"value": "new plain password"
} |
...
The following example shows how to change the login name and the password credentials for an Amazon S3 storage target in the same request. The password has to be in plain format.
...
| Code Block |
|---|
{
"bucket": "bucket name",
"region": "region",
"objectLockEnabled": true,
"objectLockMode": "compliance",
"accessKeyId": "amazons3_storage_keyid",
"id": 11,
"name": "amazonAmazon s3S3",
"type": "amazon_s3"
} |
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 a Storage Target entities can have different types with different object properties, for the password verification the verified property name has to be passed too with the checked plain password.
| Code Block |
|---|
POST https://VFC_MR_DOMAIN/verba/restapi/v1/storageTargets/11/password/verify
Content-Type: application/json
Accept: application/json
{
"property": "secretAccessKey",
"value": "new plain password"
} |
Import Source
Similar to Storage Targets the different Import Source types have different object schema representations in the REST API. The modifiable properties are depend on the specific type.
The following example shows how to change credentials for an Zoom Phones import source in one request. The password has to be in plain format.
Request
| Code Block | ||
|---|---|---|
| ||
PATCH https://VFC_MR_DOMAIN/verba/restapi/v1/importSources/1
Content-Type: application/json
Accept: application/json
{
"apiKey": "zoom_api_key",
"apiSecret": "new plain password"
} |
Response
| Code Block |
|---|
{
"authType": "jwt",
"apiKey": "zoom_api_key",
"forwardProxyAddress": "proxy address",
"forwardProxyPort": 1111,
"forwardProxyUser": "zoom_proxyuser",
"apiAddress": "https://api.zoom.us/v2/",
"id": 1,
"name": "Zoom Phone import",
"type": "zoom_phones"
} |
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 a Import Source entities can have different types with different object properties, for the password verification the verified property name has to be passed too with the checked plain password.
| Code Block |
|---|
POST https://VFC_MR_DOMAIN/verba/restapi/v1/importSources/1/password/verify
Content-Type: application/json
Accept: application/json
{
"property": "apiSecret",
"value": "new plain password"
} |