Generate As 2805 Kek Validation
| paymentcryptographydataplane_generate_as_2805_kek_validation | R Documentation |
Generates a KekValidationRequest or a KekValidationResponse for node-to-node initialization between payment processing nodes using Australian Standard 2805 (AS2805)¶
Description¶
Generates a KekValidationRequest or a KekValidationResponse for
node-to-node initialization between payment processing nodes using
Australian Standard 2805
(AS2805).
During node-to-node initialization, both communicating nodes must validate that they possess the correct Key Encrypting Keys (KEKs) before proceeding with session key exchange. In AS2805, the sending KEK (KEKs) of one node corresponds to the receiving KEK (KEKr) of its partner node. Each node uses its KEK to encrypt and decrypt session keys exchanged between the nodes. A KEK can be created or imported into Amazon Web Services Payment Cryptography using either the CreateKey or ImportKey operations.
To use generate_as_2805_kek_validation to generate a KEK validation
request, set KekValidationType to KekValidationRequest. This
operation returns both RandomKeySend (KRs) and RandomKeyReceive
(KRr) as response values. The partnering node receives the KRs, uses its
KEKr to decrypt it, and generates a KRr which is an inverted value of
KRs. The node receiving the KRr validates it against its own KRr
generated during KEK validation request outside of Amazon Web Services
Payment Cryptography.
You can also use this operation to generate a KEK validation response,
by setting KekValidationType to KekValidationResponse and providing
the incoming KRs. This operation then calculates a KRr. To learn more
about more about node-to-node initialization, see Validation of
KEK
in the Amazon Web Services Payment Cryptography User Guide.
For information about valid keys for this operation, see Understanding key attributes and Key types for specific data operations in the Amazon Web Services Payment Cryptography User Guide.
Cross-account use: This operation supports cross-account use when the key has a resource-based policy that grants access. For more information, see Resource-based policies.
Usage¶
paymentcryptographydataplane_generate_as_2805_kek_validation(
KeyIdentifier, KekValidationType, RandomKeySendVariantMask)
Arguments¶
KeyIdentifier |
[required] The |
KekValidationType |
[required] Defines whether to generate a KEK validation request or KEK validation response for node-to-node initialization. |
RandomKeySendVariantMask |
[required] The key variant to use for generating a random key for KEK validation during node-to-node initialization. |
Value¶
A list with the following syntax:
list(
KeyArn = "string",
KeyCheckValue = "string",
RandomKeySend = "string",
RandomKeyReceive = "string"
)
Request syntax¶
svc$generate_as_2805_kek_validation(
KeyIdentifier = "string",
KekValidationType = list(
KekValidationRequest = list(
DeriveKeyAlgorithm = "TDES_2KEY"|"TDES_3KEY"|"AES_128"|"AES_192"|"AES_256"|"HMAC_SHA256"|"HMAC_SHA384"|"HMAC_SHA512"|"HMAC_SHA224",
RandomKeyMaxLength = "BYTES_8"|"BYTES_16"|"BYTES_24"
),
KekValidationResponse = list(
RandomKeySend = "string"
)
),
RandomKeySendVariantMask = "VARIANT_MASK_82C0"|"VARIANT_MASK_82"
)