Signs data by using the given SignDataDetails resource.
POST {{cryptoEndpoint}}/20180608/sign
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.
Request Body
{"message"=>"<string>", "keyId"=>"<string>", "signingAlgorithm"=>"SHA_384_RSA_PKCS_PSS", "keyVersionId"=>"<string>", "messageType"=>"RAW"}
HEADERS
| Key | Datatype | Required | Description |
|---|---|---|---|
opc-request-id | string | Unique identifier for the request. If provided, the returned request ID | |
| will include this value. Otherwise, a random request ID will be | |||
| generated by the service. | |||
Content-Type | string | ||
Accept | string |
RESPONSES
status: OK
{"keyId":"\u003cstring\u003e","keyVersionId":"\u003cstring\u003e","signature":"\u003cstring\u003e","signingAlgorithm":"SHA_256_RSA_PKCS1_V1_5"}