@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class SignRequest extends AmazonWebServiceRequest implements Serializable, Cloneable
NOOP| Constructor and Description |
|---|
SignRequest() |
| Modifier and Type | Method and Description |
|---|---|
SignRequest |
clone()
Creates a shallow clone of this object for all fields except the handler context.
|
boolean |
equals(Object obj) |
Boolean |
getDryRun()
Checks if your request will succeed.
|
List<String> |
getGrantTokens()
A list of grant tokens.
|
String |
getKeyId()
Identifies an asymmetric KMS key.
|
ByteBuffer |
getMessage()
Specifies the message or message digest to sign.
|
String |
getMessageType()
Tells KMS whether the value of the
Message parameter should be hashed as part of the signing
algorithm. |
String |
getSigningAlgorithm()
Specifies the signing algorithm to use when signing the message.
|
int |
hashCode() |
Boolean |
isDryRun()
Checks if your request will succeed.
|
void |
setDryRun(Boolean dryRun)
Checks if your request will succeed.
|
void |
setGrantTokens(Collection<String> grantTokens)
A list of grant tokens.
|
void |
setKeyId(String keyId)
Identifies an asymmetric KMS key.
|
void |
setMessage(ByteBuffer message)
Specifies the message or message digest to sign.
|
void |
setMessageType(String messageType)
Tells KMS whether the value of the
Message parameter should be hashed as part of the signing
algorithm. |
void |
setSigningAlgorithm(String signingAlgorithm)
Specifies the signing algorithm to use when signing the message.
|
String |
toString()
Returns a string representation of this object.
|
SignRequest |
withDryRun(Boolean dryRun)
Checks if your request will succeed.
|
SignRequest |
withGrantTokens(Collection<String> grantTokens)
A list of grant tokens.
|
SignRequest |
withGrantTokens(String... grantTokens)
A list of grant tokens.
|
SignRequest |
withKeyId(String keyId)
Identifies an asymmetric KMS key.
|
SignRequest |
withMessage(ByteBuffer message)
Specifies the message or message digest to sign.
|
SignRequest |
withMessageType(MessageType messageType)
Tells KMS whether the value of the
Message parameter should be hashed as part of the signing
algorithm. |
SignRequest |
withMessageType(String messageType)
Tells KMS whether the value of the
Message parameter should be hashed as part of the signing
algorithm. |
SignRequest |
withSigningAlgorithm(SigningAlgorithmSpec signingAlgorithm)
Specifies the signing algorithm to use when signing the message.
|
SignRequest |
withSigningAlgorithm(String signingAlgorithm)
Specifies the signing algorithm to use when signing the message.
|
addHandlerContext, getCloneRoot, getCloneSource, getCustomQueryParameters, getCustomRequestHeaders, getGeneralProgressListener, getHandlerContext, getReadLimit, getRequestClientOptions, getRequestCredentials, getRequestCredentialsProvider, getRequestMetricCollector, getSdkClientExecutionTimeout, getSdkRequestTimeout, putCustomQueryParameter, putCustomRequestHeader, setGeneralProgressListener, setRequestCredentials, setRequestCredentialsProvider, setRequestMetricCollector, setSdkClientExecutionTimeout, setSdkRequestTimeout, withGeneralProgressListener, withRequestCredentialsProvider, withRequestMetricCollector, withSdkClientExecutionTimeout, withSdkRequestTimeoutpublic void setKeyId(String keyId)
Identifies an asymmetric KMS key. KMS uses the private key in the asymmetric KMS key to sign the message. The
KeyUsage type of the KMS key must be SIGN_VERIFY. To find the KeyUsage of
a KMS key, use the DescribeKey operation.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with
"alias/". To specify a KMS key in a different Amazon Web Services account, you must use the key ARN
or alias ARN.
For example:
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
Alias name: alias/ExampleAlias
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
keyId - Identifies an asymmetric KMS key. KMS uses the private key in the asymmetric KMS key to sign the message.
The KeyUsage type of the KMS key must be SIGN_VERIFY. To find the
KeyUsage of a KMS key, use the DescribeKey operation.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix
it with "alias/". To specify a KMS key in a different Amazon Web Services account, you must
use the key ARN or alias ARN.
For example:
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
Alias name: alias/ExampleAlias
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
public String getKeyId()
Identifies an asymmetric KMS key. KMS uses the private key in the asymmetric KMS key to sign the message. The
KeyUsage type of the KMS key must be SIGN_VERIFY. To find the KeyUsage of
a KMS key, use the DescribeKey operation.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with
"alias/". To specify a KMS key in a different Amazon Web Services account, you must use the key ARN
or alias ARN.
For example:
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
Alias name: alias/ExampleAlias
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
KeyUsage type of the KMS key must be SIGN_VERIFY. To find the
KeyUsage of a KMS key, use the DescribeKey operation.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix
it with "alias/". To specify a KMS key in a different Amazon Web Services account, you must
use the key ARN or alias ARN.
For example:
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
Alias name: alias/ExampleAlias
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
public SignRequest withKeyId(String keyId)
Identifies an asymmetric KMS key. KMS uses the private key in the asymmetric KMS key to sign the message. The
KeyUsage type of the KMS key must be SIGN_VERIFY. To find the KeyUsage of
a KMS key, use the DescribeKey operation.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix it with
"alias/". To specify a KMS key in a different Amazon Web Services account, you must use the key ARN
or alias ARN.
For example:
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
Alias name: alias/ExampleAlias
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
keyId - Identifies an asymmetric KMS key. KMS uses the private key in the asymmetric KMS key to sign the message.
The KeyUsage type of the KMS key must be SIGN_VERIFY. To find the
KeyUsage of a KMS key, use the DescribeKey operation.
To specify a KMS key, use its key ID, key ARN, alias name, or alias ARN. When using an alias name, prefix
it with "alias/". To specify a KMS key in a different Amazon Web Services account, you must
use the key ARN or alias ARN.
For example:
Key ID: 1234abcd-12ab-34cd-56ef-1234567890ab
Key ARN: arn:aws:kms:us-east-2:111122223333:key/1234abcd-12ab-34cd-56ef-1234567890ab
Alias name: alias/ExampleAlias
Alias ARN: arn:aws:kms:us-east-2:111122223333:alias/ExampleAlias
To get the key ID and key ARN for a KMS key, use ListKeys or DescribeKey. To get the alias name and alias ARN, use ListAliases.
public void setMessage(ByteBuffer message)
Specifies the message or message digest to sign. Messages can be 0-4096 bytes. To sign a larger message, provide a message digest.
If you provide a message digest, use the DIGEST value of MessageType to prevent the
digest from being hashed again while signing.
The AWS SDK for Java performs a Base64 encoding on this field before sending this request to the AWS service. Users of the SDK should not perform Base64 encoding on this field.
Warning: ByteBuffers returned by the SDK are mutable. Changes to the content or position of the byte buffer will be seen by all objects that have a reference to this object. It is recommended to call ByteBuffer.duplicate() or ByteBuffer.asReadOnlyBuffer() before using or reading from the buffer. This behavior will be changed in a future major version of the SDK.
message - Specifies the message or message digest to sign. Messages can be 0-4096 bytes. To sign a larger message,
provide a message digest.
If you provide a message digest, use the DIGEST value of MessageType to prevent
the digest from being hashed again while signing.
public ByteBuffer getMessage()
Specifies the message or message digest to sign. Messages can be 0-4096 bytes. To sign a larger message, provide a message digest.
If you provide a message digest, use the DIGEST value of MessageType to prevent the
digest from being hashed again while signing.
ByteBuffers are stateful. Calling their get methods changes their position. We recommend
using ByteBuffer.asReadOnlyBuffer() to create a read-only view of the buffer with an independent
position, and calling get methods on this rather than directly on the returned ByteBuffer.
Doing so will ensure that anyone else using the ByteBuffer will not be affected by changes to the
position.
If you provide a message digest, use the DIGEST value of MessageType to prevent
the digest from being hashed again while signing.
public SignRequest withMessage(ByteBuffer message)
Specifies the message or message digest to sign. Messages can be 0-4096 bytes. To sign a larger message, provide a message digest.
If you provide a message digest, use the DIGEST value of MessageType to prevent the
digest from being hashed again while signing.
The AWS SDK for Java performs a Base64 encoding on this field before sending this request to the AWS service. Users of the SDK should not perform Base64 encoding on this field.
Warning: ByteBuffers returned by the SDK are mutable. Changes to the content or position of the byte buffer will be seen by all objects that have a reference to this object. It is recommended to call ByteBuffer.duplicate() or ByteBuffer.asReadOnlyBuffer() before using or reading from the buffer. This behavior will be changed in a future major version of the SDK.
message - Specifies the message or message digest to sign. Messages can be 0-4096 bytes. To sign a larger message,
provide a message digest.
If you provide a message digest, use the DIGEST value of MessageType to prevent
the digest from being hashed again while signing.
public void setMessageType(String messageType)
Tells KMS whether the value of the Message parameter should be hashed as part of the signing
algorithm. Use RAW for unhashed messages; use DIGEST for message digests, which are
already hashed.
When the value of MessageType is RAW, KMS uses the standard signing algorithm, which
begins with a hash function. When the value is DIGEST, KMS skips the hashing step in the signing
algorithm.
Use the DIGEST value only when the value of the Message parameter is a message digest.
If you use the DIGEST value with an unhashed message, the security of the signing operation can be
compromised.
When the value of MessageTypeis DIGEST, the length of the Message value
must match the length of hashed messages for the specified signing algorithm.
You can submit a message digest and omit the MessageType or specify RAW so the digest
is hashed again while signing. However, this can cause verification failures when verifying with a system that
assumes a single hash.
The hashing algorithm in that Sign uses is based on the SigningAlgorithm value.
Signing algorithms that end in SHA_256 use the SHA_256 hashing algorithm.
Signing algorithms that end in SHA_384 use the SHA_384 hashing algorithm.
Signing algorithms that end in SHA_512 use the SHA_512 hashing algorithm.
SM2DSA uses the SM3 hashing algorithm. For details, see Offline verification with SM2 key pairs.
messageType - Tells KMS whether the value of the Message parameter should be hashed as part of the signing
algorithm. Use RAW for unhashed messages; use DIGEST for message digests, which
are already hashed.
When the value of MessageType is RAW, KMS uses the standard signing algorithm,
which begins with a hash function. When the value is DIGEST, KMS skips the hashing step in
the signing algorithm.
Use the DIGEST value only when the value of the Message parameter is a message
digest. If you use the DIGEST value with an unhashed message, the security of the signing
operation can be compromised.
When the value of MessageTypeis DIGEST, the length of the Message
value must match the length of hashed messages for the specified signing algorithm.
You can submit a message digest and omit the MessageType or specify RAW so the
digest is hashed again while signing. However, this can cause verification failures when verifying with a
system that assumes a single hash.
The hashing algorithm in that Sign uses is based on the SigningAlgorithm value.
Signing algorithms that end in SHA_256 use the SHA_256 hashing algorithm.
Signing algorithms that end in SHA_384 use the SHA_384 hashing algorithm.
Signing algorithms that end in SHA_512 use the SHA_512 hashing algorithm.
SM2DSA uses the SM3 hashing algorithm. For details, see Offline verification with SM2 key pairs.
MessageTypepublic String getMessageType()
Tells KMS whether the value of the Message parameter should be hashed as part of the signing
algorithm. Use RAW for unhashed messages; use DIGEST for message digests, which are
already hashed.
When the value of MessageType is RAW, KMS uses the standard signing algorithm, which
begins with a hash function. When the value is DIGEST, KMS skips the hashing step in the signing
algorithm.
Use the DIGEST value only when the value of the Message parameter is a message digest.
If you use the DIGEST value with an unhashed message, the security of the signing operation can be
compromised.
When the value of MessageTypeis DIGEST, the length of the Message value
must match the length of hashed messages for the specified signing algorithm.
You can submit a message digest and omit the MessageType or specify RAW so the digest
is hashed again while signing. However, this can cause verification failures when verifying with a system that
assumes a single hash.
The hashing algorithm in that Sign uses is based on the SigningAlgorithm value.
Signing algorithms that end in SHA_256 use the SHA_256 hashing algorithm.
Signing algorithms that end in SHA_384 use the SHA_384 hashing algorithm.
Signing algorithms that end in SHA_512 use the SHA_512 hashing algorithm.
SM2DSA uses the SM3 hashing algorithm. For details, see Offline verification with SM2 key pairs.
Message parameter should be hashed as part of the signing
algorithm. Use RAW for unhashed messages; use DIGEST for message digests, which
are already hashed.
When the value of MessageType is RAW, KMS uses the standard signing algorithm,
which begins with a hash function. When the value is DIGEST, KMS skips the hashing step in
the signing algorithm.
Use the DIGEST value only when the value of the Message parameter is a message
digest. If you use the DIGEST value with an unhashed message, the security of the signing
operation can be compromised.
When the value of MessageTypeis DIGEST, the length of the Message
value must match the length of hashed messages for the specified signing algorithm.
You can submit a message digest and omit the MessageType or specify RAW so the
digest is hashed again while signing. However, this can cause verification failures when verifying with a
system that assumes a single hash.
The hashing algorithm in that Sign uses is based on the SigningAlgorithm value.
Signing algorithms that end in SHA_256 use the SHA_256 hashing algorithm.
Signing algorithms that end in SHA_384 use the SHA_384 hashing algorithm.
Signing algorithms that end in SHA_512 use the SHA_512 hashing algorithm.
SM2DSA uses the SM3 hashing algorithm. For details, see Offline verification with SM2 key pairs.
MessageTypepublic SignRequest withMessageType(String messageType)
Tells KMS whether the value of the Message parameter should be hashed as part of the signing
algorithm. Use RAW for unhashed messages; use DIGEST for message digests, which are
already hashed.
When the value of MessageType is RAW, KMS uses the standard signing algorithm, which
begins with a hash function. When the value is DIGEST, KMS skips the hashing step in the signing
algorithm.
Use the DIGEST value only when the value of the Message parameter is a message digest.
If you use the DIGEST value with an unhashed message, the security of the signing operation can be
compromised.
When the value of MessageTypeis DIGEST, the length of the Message value
must match the length of hashed messages for the specified signing algorithm.
You can submit a message digest and omit the MessageType or specify RAW so the digest
is hashed again while signing. However, this can cause verification failures when verifying with a system that
assumes a single hash.
The hashing algorithm in that Sign uses is based on the SigningAlgorithm value.
Signing algorithms that end in SHA_256 use the SHA_256 hashing algorithm.
Signing algorithms that end in SHA_384 use the SHA_384 hashing algorithm.
Signing algorithms that end in SHA_512 use the SHA_512 hashing algorithm.
SM2DSA uses the SM3 hashing algorithm. For details, see Offline verification with SM2 key pairs.
messageType - Tells KMS whether the value of the Message parameter should be hashed as part of the signing
algorithm. Use RAW for unhashed messages; use DIGEST for message digests, which
are already hashed.
When the value of MessageType is RAW, KMS uses the standard signing algorithm,
which begins with a hash function. When the value is DIGEST, KMS skips the hashing step in
the signing algorithm.
Use the DIGEST value only when the value of the Message parameter is a message
digest. If you use the DIGEST value with an unhashed message, the security of the signing
operation can be compromised.
When the value of MessageTypeis DIGEST, the length of the Message
value must match the length of hashed messages for the specified signing algorithm.
You can submit a message digest and omit the MessageType or specify RAW so the
digest is hashed again while signing. However, this can cause verification failures when verifying with a
system that assumes a single hash.
The hashing algorithm in that Sign uses is based on the SigningAlgorithm value.
Signing algorithms that end in SHA_256 use the SHA_256 hashing algorithm.
Signing algorithms that end in SHA_384 use the SHA_384 hashing algorithm.
Signing algorithms that end in SHA_512 use the SHA_512 hashing algorithm.
SM2DSA uses the SM3 hashing algorithm. For details, see Offline verification with SM2 key pairs.
MessageTypepublic SignRequest withMessageType(MessageType messageType)
Tells KMS whether the value of the Message parameter should be hashed as part of the signing
algorithm. Use RAW for unhashed messages; use DIGEST for message digests, which are
already hashed.
When the value of MessageType is RAW, KMS uses the standard signing algorithm, which
begins with a hash function. When the value is DIGEST, KMS skips the hashing step in the signing
algorithm.
Use the DIGEST value only when the value of the Message parameter is a message digest.
If you use the DIGEST value with an unhashed message, the security of the signing operation can be
compromised.
When the value of MessageTypeis DIGEST, the length of the Message value
must match the length of hashed messages for the specified signing algorithm.
You can submit a message digest and omit the MessageType or specify RAW so the digest
is hashed again while signing. However, this can cause verification failures when verifying with a system that
assumes a single hash.
The hashing algorithm in that Sign uses is based on the SigningAlgorithm value.
Signing algorithms that end in SHA_256 use the SHA_256 hashing algorithm.
Signing algorithms that end in SHA_384 use the SHA_384 hashing algorithm.
Signing algorithms that end in SHA_512 use the SHA_512 hashing algorithm.
SM2DSA uses the SM3 hashing algorithm. For details, see Offline verification with SM2 key pairs.
messageType - Tells KMS whether the value of the Message parameter should be hashed as part of the signing
algorithm. Use RAW for unhashed messages; use DIGEST for message digests, which
are already hashed.
When the value of MessageType is RAW, KMS uses the standard signing algorithm,
which begins with a hash function. When the value is DIGEST, KMS skips the hashing step in
the signing algorithm.
Use the DIGEST value only when the value of the Message parameter is a message
digest. If you use the DIGEST value with an unhashed message, the security of the signing
operation can be compromised.
When the value of MessageTypeis DIGEST, the length of the Message
value must match the length of hashed messages for the specified signing algorithm.
You can submit a message digest and omit the MessageType or specify RAW so the
digest is hashed again while signing. However, this can cause verification failures when verifying with a
system that assumes a single hash.
The hashing algorithm in that Sign uses is based on the SigningAlgorithm value.
Signing algorithms that end in SHA_256 use the SHA_256 hashing algorithm.
Signing algorithms that end in SHA_384 use the SHA_384 hashing algorithm.
Signing algorithms that end in SHA_512 use the SHA_512 hashing algorithm.
SM2DSA uses the SM3 hashing algorithm. For details, see Offline verification with SM2 key pairs.
MessageTypepublic List<String> getGrantTokens()
A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
public void setGrantTokens(Collection<String> grantTokens)
A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
grantTokens - A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
public SignRequest withGrantTokens(String... grantTokens)
A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
NOTE: This method appends the values to the existing list (if any). Use
setGrantTokens(java.util.Collection) or withGrantTokens(java.util.Collection) if you want to
override the existing values.
grantTokens - A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
public SignRequest withGrantTokens(Collection<String> grantTokens)
A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
grantTokens - A list of grant tokens.
Use a grant token when your permission to call this operation comes from a new grant that has not yet achieved eventual consistency. For more information, see Grant token and Using a grant token in the Key Management Service Developer Guide.
public void setSigningAlgorithm(String signingAlgorithm)
Specifies the signing algorithm to use when signing the message.
Choose an algorithm that is compatible with the type and size of the specified asymmetric KMS key. When signing with RSA key pairs, RSASSA-PSS algorithms are preferred. We include RSASSA-PKCS1-v1_5 algorithms for compatibility with existing applications.
signingAlgorithm - Specifies the signing algorithm to use when signing the message.
Choose an algorithm that is compatible with the type and size of the specified asymmetric KMS key. When signing with RSA key pairs, RSASSA-PSS algorithms are preferred. We include RSASSA-PKCS1-v1_5 algorithms for compatibility with existing applications.
SigningAlgorithmSpecpublic String getSigningAlgorithm()
Specifies the signing algorithm to use when signing the message.
Choose an algorithm that is compatible with the type and size of the specified asymmetric KMS key. When signing with RSA key pairs, RSASSA-PSS algorithms are preferred. We include RSASSA-PKCS1-v1_5 algorithms for compatibility with existing applications.
Choose an algorithm that is compatible with the type and size of the specified asymmetric KMS key. When signing with RSA key pairs, RSASSA-PSS algorithms are preferred. We include RSASSA-PKCS1-v1_5 algorithms for compatibility with existing applications.
SigningAlgorithmSpecpublic SignRequest withSigningAlgorithm(String signingAlgorithm)
Specifies the signing algorithm to use when signing the message.
Choose an algorithm that is compatible with the type and size of the specified asymmetric KMS key. When signing with RSA key pairs, RSASSA-PSS algorithms are preferred. We include RSASSA-PKCS1-v1_5 algorithms for compatibility with existing applications.
signingAlgorithm - Specifies the signing algorithm to use when signing the message.
Choose an algorithm that is compatible with the type and size of the specified asymmetric KMS key. When signing with RSA key pairs, RSASSA-PSS algorithms are preferred. We include RSASSA-PKCS1-v1_5 algorithms for compatibility with existing applications.
SigningAlgorithmSpecpublic SignRequest withSigningAlgorithm(SigningAlgorithmSpec signingAlgorithm)
Specifies the signing algorithm to use when signing the message.
Choose an algorithm that is compatible with the type and size of the specified asymmetric KMS key. When signing with RSA key pairs, RSASSA-PSS algorithms are preferred. We include RSASSA-PKCS1-v1_5 algorithms for compatibility with existing applications.
signingAlgorithm - Specifies the signing algorithm to use when signing the message.
Choose an algorithm that is compatible with the type and size of the specified asymmetric KMS key. When signing with RSA key pairs, RSASSA-PSS algorithms are preferred. We include RSASSA-PKCS1-v1_5 algorithms for compatibility with existing applications.
SigningAlgorithmSpecpublic void setDryRun(Boolean dryRun)
Checks if your request will succeed. DryRun is an optional parameter.
To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.
dryRun - Checks if your request will succeed. DryRun is an optional parameter.
To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.
public Boolean getDryRun()
Checks if your request will succeed. DryRun is an optional parameter.
To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.
DryRun is an optional parameter.
To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.
public SignRequest withDryRun(Boolean dryRun)
Checks if your request will succeed. DryRun is an optional parameter.
To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.
dryRun - Checks if your request will succeed. DryRun is an optional parameter.
To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.
public Boolean isDryRun()
Checks if your request will succeed. DryRun is an optional parameter.
To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.
DryRun is an optional parameter.
To learn more about how to use this parameter, see Testing your KMS API calls in the Key Management Service Developer Guide.
public String toString()
toString in class ObjectObject.toString()public SignRequest clone()
AmazonWebServiceRequestclone in class AmazonWebServiceRequestObject.clone()