

Administration Guide › Log Storage › Configuring Non-Interactive Authentication for Restore › Example: Configure Authentication From a Storage Server to a Reporting Server › Update the Existing Public Key File
Update the Existing Public Key File
You copied the public key, authorized_keys_RSS, to the /tmp directory on the reporting server. Now you prepare the existing public key file for use. Preparation involves appending the authorized_keys_RSS to authorized_keys. The correct ownership and permissions are already set on the existing authorized_keys file.
To append authorized_keys_RSS to authorized_keys and copy it to the correct location
- Log into the reporting CA User Activity Reporting Module server through ssh as caelmadmin.
- Switch users to root.
- Change directories to the /tmp directory containing authorized_keys_RSS.
- Copy the existing authorized_keys from .ssh to the current directory, /tmp.
cp /opt/CA/LogManager/.ssh/authorized_keys .
- Add the contents of the public key from the remote storage server to the authorized_keys file that contains public keys from collection servers.
cat authorized_keys_RSS >> authorized_keys
- Change directories to /opt/CA/LogManager/.ssh.
- Copy the authorized_keys file from /tmp to.ssh, the current directory:
cp /tmp/authorized_keys .
Copyright © 2013 CA.
All rights reserved.
 
|
|