Update KMS Providers
Update an existing provider. if you do not have all of the privileges described as follows: - Operation execution requires Cryptographer.ManageKeyServers.
Request
URLURL
https://{api_host}/api/vcenter/crypto-manager/kms/providers/{provider}
Path Parameters
Path Parameters
string
provider
Required
Identifier of the provider. The parameter must be an identifier for the resource type: com.vmware.vcenter.crypto_manager.kms.provider.
Header Parameters
Header Parameters
string
vmware-api-session-id
Required
Required session ID, acquired from Create Session API under CIS product
vmware-api-session-id example
"b00db39f948d13ea1e59b4d6fce56389"
Request Body
Request Body
{
"native_spec": {
"key_id": "string"
}
}
native_spec
Optional
New Configuration for NATIVE provider.
If unset, provider configuration will remain unchanged.
Authentication
This operation uses the following authentication methods.
cURL Command
curl -X PATCH -H "vmware-api-session-id: b00db39f948d13ea1e59b4d6fce56389" -H "Content-Type: application/json" -d '{"native_spec":{"key_id":"string"}}' https://{api_host}/api/vcenter/crypto-manager/kms/providers/{provider}
Errors
400
com.vmware.vapi.std.errors.invalid_argument : if the spec is invalid. | com.vmware.vapi.std.errors.unsupported : if the provider’s type does not allow updates.
Vendor Extensions
Vendor Extensions
This operation contains the following vendor extensions defined in the spec:
x-vmw-doc-operation: update
Availability
Added in 7.0.2.0
On This Page
KMS Providers Operations
post
patch
delete
post
