Opening the wallet or hardware keystore
The security administrator must make the accessible to the database before Oracle TDE can perform any encryption or decryption. This is comparable to opening the Oracle wallet or logging in to the hardware keystore. You can open the wallet or hardware keystore manually or automatically, but the manual option requires you to re-enable access to the HSM every time the database is restarted.
Select one of the following methods and perform the instructions:
Run the following command to manually open the hardware keystore, making the HSM accessible:
Optionally, disable access with the following command:
You must re-enable access to the HSM every time you restart the database instance with the manual option.
An auto-login wallet stores the HSM credentials in an auto-login software keystore. This configuration reduces the system security, but it supports unmanned or automated operations. Also, it helps with deployments that require the HSM to re-login automatically.
Create the C:\WALLET\tde directory path.
Set the WALLET_ROOT parameter to the WALLETS directory created in the first step.
Set the TDE_CONFIGURATION parameter to FILE for the KEYSTORE_CONFIGURATION.
Stop and restart the database after setting the WALLET_ROOT and TDE_CONFIGURATION parameters.
If you have not migrated from a software keystore, create the software keystore with the hardware keystore password in the appropriate location (such as C:\WALLETS\tde).
Set the Software_Keystore_Password value to any password you choose.
Open the new software keystore with the following command:
Add the secret to the software keystore. The secret is the HSM identity password, and the client is HSM_PASSWORD. HSM_PASSWORD is an Oracle-defined client name representing the HSM password as a secret in the software keystore.
You must provide the secret and HSM_PASSWORD values within single quotes, or the command fails.
Create a new auto-login keystore by using the password of the Oracle software wallet.
Reset the TDE_CONFIGURATION parameter to HSM|FILE for the KEYSTORE_CONFIGURATION.
Stop and restart the database after setting the TDE_CONFIGURATION parameter.
At this stage, the hardware security module auto-login keystore opens automatically the next time a TDE operation executes. To confirm that the auto-login wallet is working, run the following query:
If the auto-login wallet was configured properly, the following output appears:
An auto-login wallet stores the HSM credentials in an auto-login software keystore. This configuration reduces the system security, but it supports unmanned or automated operations. Also, it helps with deployments that require the HSM to re-login automatically.
Create the /etc/ORACLE/WALLETS/tde directory path by using the mkdir command:
Change ownership of the /etc/ORACLE directory to the Oracle user.
Set the WALLET_ROOT parameter to the WALLETS directory created in the first step.
Set the TDE_CONFIGURATION parameter to FILE for the KEYSTORE_CONFIGURATION.
Stop and restart the database after setting the WALLET_ROOT and TDE_CONFIGURATION parameters.
If you have not migrated from a software keystore, create the software keystore with the hardware keystore password in the appropriate location (such as /etc/ORACLE/WALLETS/tde).
Set the Software_Keystore_Password value to any password you choose.
Open the new software keystore with the following command:
Add the secret to the software keystore. The secret is the HSM identity password, and client is HSM_PASSWORD. HSM_PASSWORD is an Oracle-defined client name representing the HSM password as a secret in the software keystore.
You must provide the secret and HSM_PASSWORD values within single quotes, or the command fails.
Create a new auto-login keystore by using the password of the Oracle software wallet.
Reset the TDE_CONFIGURATION parameter to HSM|FILE for the KEYSTORE_CONFIGURATION.
Stop and restart the database after setting the TDE_CONFIGURATION parameter.
At this stage, the hardware security module auto-login keystore opens automatically the next time a TDE operation executes. To confirm that the auto-login wallet is working, run the following query:
If the auto-login wallet was configured properly, the following output appears: