Open topic with navigation
The following procedure describes the algorithm to use to decrypt a security info string that is encrypted with an AES key file, with optional HMAC validation.
To decrypt a security info string, you need the AES key file that was used to generate it. HPE strongly recommends that you secure your AES key file so that only your IDOL components and authorized administrators can access it.
The IDOL Content component, IDOL Community component and DAH need access to the key file.
To decrypt an AES SecurityInfo String
Base64 decode the SecurityInfo String.
Split the decoded string on the left-most pipe character (
The left side is the data length. The right side is the data (with the digest, if you use HMAC validation).
Check that the data length is equal to the length of the data with digest. If this check is not successful, fail the decryption.
(Optional) Use the following steps for HMAC validation:
Split the data with digest on the left-most pipe character (
The left side is the digest hex string. The right side is the data.
Generate the HMAC key by taking a SHA-1 hash of your AES hexadecimal key string.
This operation makes the key string case-sensitive.
Calculate the HMAC_SHA512 value of the data.
Select the first 16 bytes of the data. This is the AES initialization vector.
Use AES-CBC to decrypt the remaining data, by using the IV and the 256-bit key from your AES hexadecimal key string.
The decrypted data has the prefix
AUTN:. If this string is not present, fail the decryption.