Setting up a secure channel between the NetBackup BAR Console and bpjava-*
The following steps describe the process flow to set up a secure channel between the NetBackup BAR Console and bpjava-*:
Note:
The following processes are used: bpjava-msvc, which controls the login and authentication; bpjava-susvc, which is the BAR console process; and bpjava-usvc, which is the client Backup, Archive, and Restore (BAR) interface.
The user initiates a login to the console. The credentials are sent to bpjava-msvc over the SSL (using the Server Security Certificate).
The bpjava-msvc process authenticates the user who uses the user credentials that were received in step 1.
After the user is authenticated, the bpjava-msvc process performs the following:
Generates the entities that are called the self-signed session certificate, the key, and the session token.
Launches the daemon bpjava-*usvc to gather more requests from the NetBackup BAR Console.
Passes the self-signed session certificate and the session token to bpjava-*usvc.
Note:
The bpjava-*usvc process uses a session certificate as a Server Security Certificate for the SSL channel. It uses the session token to authenticate the NetBackup BAR Console. The console does not use credentials while it connects to the bpjava-*usvc process. The NetBackup BAR Console uses the session token for authentication.
Sends the session token and the fingerprint of the session certificate to the NetBackup BAR Console.
Persists session token and user information to a secure directory (
install_path/var; for example,/usr/openv/var) in a file on the NetBackup host. This directory is accessible only to the root/administrator. The file name format is as follows:hash(session token)_bpjava-*usvc_pid
Note:
msvc saves this information so it can be used by nbsl or nbvault to authenticate the NetBackup BAR Console.
The msvc process stops the execution and exits.
bpjava-*usvc uses the session certificate to start the secure channel with the NetBackup BAR Console. This secure channel is a one-way authenticated SSL channel. (Only the server certificate is present and there is no peer certificate. There is no certificate from the NetBackup BAR Console side.)
The NetBackup BAR Console receives the session certificate as a part of the initial SSL handshake. It verifies the authenticity of the session certificate by using the pre-existing fingerprint of the session certificate (see step 3). The NetBackup BAR Console calculates the fingerprint of the session certificate that was received from bpjava-*usvc due to the SSL handshake. It compares the new fingerprint with the fingerprint sent by msvc.
Once the authenticity of the certificate is verified, the NetBackup BAR Console sends the session token (received in step 3) to bpjava-*usvc.
bpjava-*usvc verifies the received session token with the pre-existing one (see step 3).
The success of the session token validation creates trust between bpjava-*usvc and the NetBackup BAR Console.
All further communication occurs between bpjava-*usvc and the NetBackup BAR Console on this trusted secure channel.