Wednesday, July 24, 2024

Oracle Key Vault 21.9 Installation Steps in guest VM

 Oracle Key Vault Installation Steps in Guest VM

Reference: 

https://docs.oracle.com/en/database/oracle/key-vault/21.8/okvig/installing-oracle-key-vault.html#GUID-BCCBB58F-FABD-4CAB-9427-07767D7FEB70

https://docs.oracle.com/en/database/oracle/key-vault/21.9/okvig/installing-oracle-key-vault.html#GUID-BCCBB58F-FABD-4CAB-9427-07767D7FEB70

Please note there is no difference in the install procedure between 21.8 and 21.9, I did compare the install doc using diff utility, there is no concerning change.

  1. Ensure prereqs are complete

  2. OKV can be installed in either a dedicated physical hardware or a virtual machine

  3. Secure a fixed IP address from the network team

IP

192.168.194.121

Subnet mask

255.255.255.0

gateway

192.168.194.1

  1. Validate access to the iso file downloaded.


D:\Downloads\OracleBin\21.8>dir

 Volume in drive D is SSD2

 Volume Serial Number is 647C-3B8C


 Directory of D:\Downloads\OracleBin\21.8


01/07/2024  06:40    <DIR>          .

01/07/2024  06:40    <DIR>          ..

01/07/2024  07:13    20,894,973,952 V1041311-01.iso

               1 File(s) 20,894,973,952 bytes

               2 Dir(s)  166,817,976,320 bytes free


D:\Downloads\OracleBin\21.8>


  1. Mount the iso file into the DVD drive of the VM and boot it

  2. Choose “Press Enter to start the installation of the Oracle Key Vault”

  3. On prompt enter root password, remember to note it down, since you will need to set other credentials which manages the OKV at a later stage

  4. When prompted enter root password and then press enter again to monitor the installation

  5. Re-insert the ISO file if needed

  6. Choose classic vs dual-nic mode, since ours is Virtual all, we will choose classic mode (1 interface)

    1. Enter ip, subnet mask and gateway details we populated in the beginning

  7. The install continues then to complete the installation of self-contained hardened appliance.

  8. Once install is complete, use the terminal to login as root and set the password for support user (a user which is used for most of the BAU routines like patching, upgrade etc..)

  9. SSH is enabled only to allow support user login.

  10. The SSH by default should stay disabled unless upgrade patches are applied.

Post installation steps for OKV:

  1. You may not be able to access the appliance you just finished installing using ssh. The ssh to the 192.168.194.122 might fail with below error.


  1. But the above error isn’t a concern. Ensure you have already set password for support user in the terminal.

  2. The post install mainly involves setting up

    1. Setting up administrative user accounts - one time passwords

    2. The recovery passphrase

    3. DNS and NTP settings

  3. Using web browser we need to connect to the below url:

https://192.168.194.122


It will report its not secure, but just proceed, since the certificate isn’t installed yet. This message pops up.

  1. Use root password, for the post install (only once) config, the OKV will directly prompt for the root password®. Login with the root password and then create

    1. Key admin

    2. System admin

    3. Audit manager

If there is only OKV admin, you can keep all 3 as same user for instance “admin” for key admin and then reference the same for other 2 admin accounts as well. Grant forward option allows the users to grant their to other users on their own.

  1. Recovery passphrase needs to be enabled, the recovery passphrase is very important when it comes to emergency situation listed below…

    1. OKV restore

    2. Loss or inaccessibility of one of the admin accounts

    3. Multimaster node addition

    4. To reset recovery passphrase

    5. To configure a HSM

  2. The root and support user passwords will expire after 365 days, hence we need to ensure they are changed regularly. If you end up logging in 120 days window of the password expiry, you will get a prompt and you can change the password. If not after expiry it is mandatory to change the password before login.

  3. Next step involves DNS and NTP config.

  4. Alert configuration


YouTube Video:


No comments:

Post a Comment

Flashback data archive steps

 Objective: Ways to track DML changes in a table Detailed objective: We should be able to track the changes in the table at any point in tim...