All ACI communication actions sent to IDOL components in an OEM-licensed environment must be ACI encrypted. IDOL components access the licensekey.dat
file to determine the encryption keys required to decode encrypted action.
You must not use the CommsEncryptionType
and CommsEncryptionTEAKeys
(deprecated) configuration parameters to encrypt ACI communications because the key would be publicly available.
To set up licensing in an OEM environment
Encrypt ACI communications between IDOL components and the front-end application by making the appropriate API call in your application and passing in the OEM encryption keys that were provided to you. For example:
In the C API, you could make the following call:
char* szKeys = "MjR8CJCUGcb4RbRdNDKbK9RXX3pEswAiZ"; aciInitEncryption(TRUE, "TEA", szKeys);
where the value of szKeys
is the encryption key provided with the license.
In the Java API, you could make the following call:
TEAEncryptionDetails encryptionDetails = new TEAEncryptionDetails(); encryptionDetails.setEncryptionKeys(MjR8CJCUGcb4RbRdNDKbK9RXX3pEswAiZ); encryptionDetails.setEncrypting(true); aciConnection.setEncryptionDetails(encrytionDetails);
Redistribute the licensekey.dat
file with your application by copying it to the working directory of each IDOL component. The IDOL components will then read the license from the licensekey.dat
instead of the [License]
section of the component’s configuration file.
The licensekey.dat
file is generated by Micro Focus and provided to you along with your license.
EncryptResponse
action parameter to True
in the ACI action you run. However, in most cases HPE recommends that you use SSL/TLS for secure communications.
|