Fortinet black logo

Handbook (HTML)

SSH environment requirements (software-only version)

Copy Link
Copy Doc ID 73ac471a-9afd-11ea-8862-00505692583a:842271

SSH environment requirements (software-only version)

When you use the software-only version of FortiDB, the following SSH environment is required to allow FortiDB to connect to target databases using a SSH connection.

In addition, for some Oracle databases, additional configuration is required to use the operating system vulnerability assessment (OSVA) feature.

If you need help setting up a working SSH environment, contact your System Administrator.

The target configuration SSH tab provides two Access Method options: Implicit Key Pair (key pair is specified by the SSH Key File global property) and Explicit Key Pair (the key pair information is specified on the SSH tab). For more information on the SSH tab, see Configuring SSH connections to Oracle and DB2 databases.

Item Description
Public Key handling For either the Explicit Key Pair or Implicit Key Pair methods, use secure copy (SCP) to copy the public key that you generate on the SSH client to your SSH server. Then, append the key to the authorized_keys file located in the .ssh directory within the home directory of the FortiDB SSH user.
Private Key handling

For either the Explicit Key Pairor Implicit Key Pair methods, generate id_dsa or id_rsa private keys and copy them to the .ssh directory under user's home directory on the SSH client machine.

In a Windows environment, the private key resides in the /.ssh directory under the user's home directories. The exact directory depends on the OS version. For example, C:\Documents and Settings\All Users.

SSH Client Location The SSH client runs on your FortiDB machine.
SSH Server Location The SSH server runs on your target database machine.
User account for SSH User To configure a SSH connection, a user account on your target database machine is required.
DB2 Target Specific Instructions

In some cases, additional configuration is required for the FortiDB OS user that you created on a DB2 target database machine.

For example, if the user is db2inst3 and you use the bash shell, add the following entry to your .bashrc file:

if [ -f /home/db2inst3/sqllib/db2profile ]; then
. /home/db2inst3/sqllib/db2profile
fi

Operating system vulnerability assessment (OSVA) with Oracle targets

If the target is an Oracle database on Solaris, to use the FortiDB operating system vulnerability assessment (OSVA) feature, specify the Home Directory, Owner, and owner's Group of your target database.

For more information on these settings, see Enabling operating system vulnerability assessment (OSVA) for Solaris and AIX.

SSH environment requirements (software-only version)

When you use the software-only version of FortiDB, the following SSH environment is required to allow FortiDB to connect to target databases using a SSH connection.

In addition, for some Oracle databases, additional configuration is required to use the operating system vulnerability assessment (OSVA) feature.

If you need help setting up a working SSH environment, contact your System Administrator.

The target configuration SSH tab provides two Access Method options: Implicit Key Pair (key pair is specified by the SSH Key File global property) and Explicit Key Pair (the key pair information is specified on the SSH tab). For more information on the SSH tab, see Configuring SSH connections to Oracle and DB2 databases.

Item Description
Public Key handling For either the Explicit Key Pair or Implicit Key Pair methods, use secure copy (SCP) to copy the public key that you generate on the SSH client to your SSH server. Then, append the key to the authorized_keys file located in the .ssh directory within the home directory of the FortiDB SSH user.
Private Key handling

For either the Explicit Key Pairor Implicit Key Pair methods, generate id_dsa or id_rsa private keys and copy them to the .ssh directory under user's home directory on the SSH client machine.

In a Windows environment, the private key resides in the /.ssh directory under the user's home directories. The exact directory depends on the OS version. For example, C:\Documents and Settings\All Users.

SSH Client Location The SSH client runs on your FortiDB machine.
SSH Server Location The SSH server runs on your target database machine.
User account for SSH User To configure a SSH connection, a user account on your target database machine is required.
DB2 Target Specific Instructions

In some cases, additional configuration is required for the FortiDB OS user that you created on a DB2 target database machine.

For example, if the user is db2inst3 and you use the bash shell, add the following entry to your .bashrc file:

if [ -f /home/db2inst3/sqllib/db2profile ]; then
. /home/db2inst3/sqllib/db2profile
fi

Operating system vulnerability assessment (OSVA) with Oracle targets

If the target is an Oracle database on Solaris, to use the FortiDB operating system vulnerability assessment (OSVA) feature, specify the Home Directory, Owner, and owner's Group of your target database.

For more information on these settings, see Enabling operating system vulnerability assessment (OSVA) for Solaris and AIX.