NetBackup™ 10.3.0.1 Application Guide
- Product overview
- Release notes
- Geting started
- Creating NetBackup application instances
- Managing NetBackup application instances
- Accessing NetBackup primary and media server instances for management tasks
- Managing users on a primary or a media server instance
- Running NetBackup commands on a primary or a media server application instance
- Managing users on a primary or a media server instance
- Accessing NetBackup WORM storage server instances for management tasks
- Managing users from the deduplication shell
- Managing certificates from the deduplication shell
- Configuring an isolated recovery environment using the web UI
- Managing NetBackup services from the deduplication shell
- Monitoring and troubleshooting NetBackup services from the deduplication shell
- Managing S3 service from the deduplication shell
- Managing users from the deduplication shell
Using SSH keys for authentication on a primary or a media server instance
You can configure a primary or a media server application instance to allow users to log in with SSH keys instead of passwords. You must already have a public and private key pair for each user. You can generate the keys with the ssh-keygen utility.
The user who wants to log in with SSH keys must work together with the appadmin user to configure authentication.
The appadmin user must create an sshkeys
directory for the other user. Use the following steps.
To create an sshkeys
directory
- Open an SSH session to the instance as the appadmin user.
- Run the following command to create the new directory:
sudo mkdir -p /var/sshkeys/<user>
Where <user> is the username of the user to provide access to.
- Run the following command to change the ownership of the directory to the other user:
sudo chown <user> /var/sshkeys/<user>
- Run the following command and check the output:
sudo grep AuthenticationMethods /etc/ssh/sshd_config
Then do one of the following:
If the output does not have any entries, or if any entries begin with a #, no action is required.
If publickey is present in the list before keyboard-interactive, no action is required.
If publickey is not present, run the following command to edit the file:
sudo vi /etc/ssh/sshd_config
Add publickey before keyboard-interactive.
The other user must copy their public SSH key to the instance. Use the following steps.
To copy the key to the instance
- From the host that you want to connect from, run the following command:
ssh-copy-id <user>@<instance>
Where <user> is your username, and <instance> is the hostname or the IP address of the instance.
- Open an SSH session to the instance and log in with your username and password.
- Run the following command:
mv ~/.ssh/authorized_keys /var/sshkeys/<user>
- Log out of the instance. You should now be able to log back in without a password.