1.0.0
- 1.0.0
- Initial record
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
ResolveAuthActions takes an encrypted record and determines the CryptoActions originally used for encryption.
It makes no network calls and does no encryption nor decryption.
The following inputs to this behavior are REQUIRED:
The logical name for the structure. This can be the same as the physical name. For example the name of the table to hold the encrypted record.
The Auth List describes how each Terminal Data would be treated during decryption.
The header and footer fields (aws_dbe_head and aws_dbe_foot) can be present, but they need not be present.
Data members need not contain any particular values.
The sequence of bytes representing the serialized header, as is usually found in the aws_dbe_head attribute.
This operation MUST output the following:
Crypto List: Input terminal data and the Crypto Schema for each Terminal, calculated using the Crypto Legend in the header, the signature scope used for decryption, and the data in the input structure.
Resolve Auth Actions examines the configuration and the provided header to determine the Crypto Actions originally use for encryption.
The data members are returned unchanged and unexamined.