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.

The top level –endpoint parameter must be supplied for this operation.


oci kms crypto verified-data verify [OPTIONS]

Required Parameters

--key-id [text]

The OCID of the key used to sign the message.

--key-version-id [text]

The OCID of the key version used to sign the message.

--message [text]

The base64-encoded binary data object denoting the message or message digest to sign. You can have a message up to 4096 bytes in size. To sign a larger message, provide the message digest.

--signature [text]

The base64-encoded binary data object denoting the cryptographic signature generated for the message.

--signing-algorithm [text]

The algorithm to use to sign the message or message digest. For RSA keys, supported signature schemes include PKCS #1 and RSASSA-PSS, along with different hashing algorithms. For ECDSA keys, ECDSA is the supported signature scheme with different hashing algorithms. When you pass a message digest for signing, ensure that you specify the same hashing algorithm as used when creating the message digest.

Accepted values are:


Optional Parameters

--from-json [text]

Provide input to this command as a JSON document from a file using the file://path-to/file syntax.

The --generate-full-command-json-input option can be used to generate a sample json file to be used with this command option. The key names are pre-populated and match the command option names (converted to camelCase format, e.g. compartment-id –> compartmentId), while the values of the keys need to be populated by the user before using the sample file as an input to this command. For any command option that accepts multiple values, the value of the key can be a JSON array.

Options can still be provided on the command line. If an option exists in both the JSON document and the command line then the command line specified value will be used.

For examples on usage of this option, please see our “using CLI with advanced JSON options” link:

--message-type [text]

Denotes whether the value of the message parameter is a raw message or a message digest. The default value, RAW, indicates a message. To indicate a message digest, use DIGEST.

Accepted values are:


Example using required parameter

Copy and paste the following example into a JSON file, replacing the example parameters with your own.

    oci kms management key create --generate-param-json-input key-shape > key-shape.json

Copy the following CLI commands into a file named Run the command by typing “bash” and replacing the example parameters with your own.

Please note this sample will only work in the POSIX-compliant bash-like shell. You need to set up the OCI configuration and appropriate security policies before trying the examples.

    export compartment_id=<substitute-value-of-compartment_id> #
    export display_name=<substitute-value-of-display_name> #
    export key_id=<substitute-value-of-key_id> #
    export message=<substitute-value-of-message> #
    export signature=<substitute-value-of-signature> #
    export signing_algorithm=<substitute-value-of-signing_algorithm> #

    key_id=$(oci kms management key create --compartment-id $compartment_id --display-name $display_name --endpoint --key-shape file://key-shape.json --query --raw-output)

    key_version_id=$(oci kms management key-version create --key-id $key_id --query --raw-output)

    oci kms crypto verified-data verify --key-id $key_id --key-version-id $key_version_id --message $message --signature $signature --signing-algorithm $signing_algorithm