FAQ On Encryption Method Used By Oracle Hyperion EPM
(Doc ID 1447233.1)
Last updated on OCTOBER 10, 2022
Applies to:
Hyperion Planning - Version 11.1.2.1.000 and later Information in this document applies to any platform.
Purpose
Frequently asked questions on Hyperion EPM Encryption.
1. What is the encryption method used in Hyperion EPM System? 2. Are the passwords masked when keyed in? 3. Where are the encrypted passwords stored? 4. Which user account(s) need to access the encrypted passwords? 5. What encryption algorithm is used to encrypt each of the passwords? 6. What is the encryption key length? 7. Where is the encryption key stored? 8. How is the encryption key protected? 9. How is the encryption key generated? 10.The AES-128 encryption key used by Hyperion Shared Services is stored in clear or masked ? 11.The very initial db connection password used by Hyperion to access the EPM System Registry (DB) is stored in a file called reg.properties? 12.The password is similarly AES-128bit encrypted. Where is the AES-128 bit encryption key used by the Hyperion Shared Services to access the System Registry stored? 13.How is it possible to store the password in the same System Registry (DB) since a connection to the (System Registry) database must first be established? 14.Where is this AES-128 bit encryption key used by the HSS stored? How is it protected in storage?
15. Is the User password encrypted when passed from the user browser to the webserver at sign in ?
Questions and Answers
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
