Get the endpoint that is being used to call (ex, https://www.example.com).
Sets the endpoint to call (ex, https://www.example.com).
The endpoint of the service.
Determines whether realm specific endpoint should be used or not. Set realmSpecificEndpointTemplateEnabled to "true" if the user wants to enable use of realm specific endpoint template, otherwise set it to "false"
flag to enable the use of realm specific endpoint template
Close the client once it is no longer needed
Decrypts data using the given DecryptDataDetails resource.
This operation does not retry by default if the user has not defined a retry configuration.
DecryptResponse
Encrypts data using the given EncryptDataDetails resource. Plaintext included in the example request is a base64-encoded value of a UTF-8 string.
This operation does not retry by default if the user has not defined a retry configuration.
EncryptResponse
Exports a specific version of a master encryption key according to the details of the request. For their protection,
keys that you create and store on a hardware security module (HSM) can never leave the HSM. You can only export keys
stored on the server. For export, the key version is encrypted by an RSA public key that you provide.
This operation is not supported for keys having protection mode EXTERNAL
.
This operation does not retry by default if the user has not defined a retry configuration.
ExportKeyResponse
Generates a key that you can use to encrypt or decrypt data.
This operation does not retry by default if the user has not defined a retry configuration.
GenerateDataEncryptionKeyResponse
Shutdown the circuit breaker used by the client when it is no longer needed
Creates a digital signature for a message or message digest by using the private key of a public-private key pair,
also known as an asymmetric key. To verify the generated signature, you can use the Verify
operation. Or, if you want to validate the signature outside of the service, you can do so by using the public key of the same asymmetric key.
This operation is not supported for keys having protection mode EXTERNAL
.
This operation does not retry by default if the user has not defined a retry configuration.
SignResponse
Verifies a digital signature that was generated by the Sign operation
by using the public key of the same asymmetric key that was used to sign the data. If you want to validate the
digital signature outside of the service, you can do so by using the public key of the asymmetric key.
This operation is not supported for keys having protection mode EXTERNAL
.
This operation does not retry by default if the user has not defined a retry configuration.
VerifyResponse
This service client uses {@link common.CircuitBreaker.DefaultConfiguration} for all the operations by default if no circuit breaker configuration is defined by the user.