Oracle Kye-vault Installation (Version 21.4 ) ( Chapter -II )
Chapter -2: (End point Configuration)
1.
This figure illustrates how a multi-master
cluster environment can be used to manage different kinds of encrypted data. It
has the following components:
- Oracle Database refers
to Oracle databases that are connected to the Oracle Key Vault. Typically,
these databases are protected with Transparent Data Encryption (TDE).
- Oracle wallets and Java keystores are containers for keys and sensitive objects
that you upload and download between Oracle Key Vault and endpoints.
- Secrets Management refers
to other keystore files, which are security objects like certificates, and
credential files like Kerberos keytab files, SSH key files, and server
password files, that you upload to Oracle Key Vault from endpoints.
- ZDLRA, MongoDB, MySQL,
GoldenGate, Solaris Crypto Keys, and ACFS are all sources of encrypted key data that can be
protected by Oracle Key Vault.
You can deploy Oracle Key Vault in the
following types of environments:
- Single Oracle Database instance
- Multiple Oracle databases on
the same server
- Oracle Database using a
multitenant environment
- Oracle GoldenGate
- Oracle Data Guard
- Oracle Exadata, engineered
systems
- Oracle Exadata Cloud@Customer
- Oracle Autonomous Database
(dedicated)
I will show here a simple deployment of
stand-alone end point for Oracle DB server.
Below are the different types of roles you can
define for maintenance but for creating end point we should use SYSADMIN role
only.
- System Administrator role provides privileges for creating and managing
users, creating and managing endpoints, configuring system settings and
alerts, and generally administering Oracle Key Vault. This is the most
powerful role.
- Key Administrator role provides privileges for managing the key life
cycle and controlling access to all security objects in Oracle Key Vault.
- Audit Manager role provides privileges for managing the audit
life cycle and audit policies.
1st add an end point using the DB name & OS
details.
Then keep the enrollment token copied for the registration
phase.
Now open the UI & don’t login yet. Click the indicated
link
Now put the token when prompted.
After pressing submit token it will validate the token &
will show you all info.
Then press the enroll button.
okvclient.jar
contains the
following:
·
A Transport Layer Security (TLS) certificate and private key
that the endpoint uses to authenticate itself to Oracle Key Vault
·
A TLS certificate for Oracle Key Vault that serves as the root
CA
·
Endpoint libraries and utilities
·
Additional information such as the Oracle Key Vault IP address
that is used by okvutil
to create the okvclient.ora
configuration
file
In
an Oracle Real Application Clusters (RAC) environment, you must enroll and
provision each Oracle RAC node as an endpoint. Each Oracle RAC-enabled database
corresponds to one virtual wallet in Oracle Key Vault. Each Oracle RAC instance
of that database corresponds to an endpoint in Oracle Key Vault. All endpoints
for each database share the same wallet as their default wallet. You must
download one distinct okvclient.jar
for each
instance.
Then it will download the okvclient.jar file.
Now copy this to your DB server. And then do the following
things.
Create dir parallel to ORACLE_HOME as okv_home
Set the JAVA path to $ORACLE_HOME/jdk/bin.
Copy the okvclient.jar file to the okv_home
Now install it by the following command.
java -jar okvclient.jar -d
/u01/app/oracle/product/19.0.0/okv_home -v
It will ask for pw for login, you can skip it for auto login
also.
After successful installation it will automatically delete
the .jar file for security reasons. And it will create the following files in
the okv_home DIR.
And then you can login to your Key-vault console to verify your
server end point details. You should notice the IP address which was blank now
have been updated with the end point server details.
So, your end-point configuration with sysadmin privileged
user has been successful. You can now start transferring your wallets, keys, etc..
*********************************************************************************
Chapter -3 (Transferring / retrieving keys) .... continues...!!!
Comments
Post a Comment