When RSA Authentication Manager 8.x services are down, direct SSH access to the server may be needed to copy files for investigation (e.g., log files or debug scripts). Normally, SSH is enabled through the Operations Console — but if the Operations Console is unavailable (for example, due to unknown credentials), SSH cannot be enabled through the standard UI method. This article describes how to enable SSH directly from the appliance console as an alternative.

Prerequisites:

• Physical or virtual console access to the Authentication Manager server (hardware keyboard/monitor, or hypervisor VM console such as VMware vSphere)
• rsaadmin operating system account credentials
• TCP port 22 must not be blocked by a firewall between your SSH client and the Authentication Manager server

Task 1: Enable SSH

1. Open a console connection to the Authentication Manager server:
   • Hardware appliance: Connect a keyboard and monitor directly to the server.
   • Virtual machine: Open the VM console from your hypervisor client (e.g., VMware vSphere Console).
2. Log in as rsaadmin and enter the operating system password when prompted
3. Escalate to root:
   

   sudo su -

   Enter the rsaadmin operating system password when prompted.

4. Run the following command to enable SSH:
   
   

   /opt/rsa/am/utils/bin/appliance/configureSSH.sh enable

    Expected output: 
   

   Shutting down the listening SSH daemon                               done
   Checking for missing server keys in /etc/ssh
   Starting SSH daemon                                                  done
   Saving iptables configuration                                        done
   Saving iptables configuration                                        done

Verification: Open an SSH client (e.g., PuTTY) and connect to the appliance IP address. Confirm you can log in successfully as rsaadmin.

Task 2: Disable SSH

1. From the appliance console (or via SSH if still connected), ensure you are logged in as root. If not, repeat Steps 2–3 from Task 1.

2. Run the following command to disable SSH:

   /opt/rsa/am/utils/bin/appliance/configureSSH.sh disable

   Expected output:

   Shutting down the listening SSH daemon                               done
   Saving iptables configuration                                        done
   Saving iptables configuration                                        done

Verification: Attempt to connect to the appliance via SSH. Confirm the connection is refused, confirming SSH has been successfully disabled.

Standard Method — Enable SSH via the Operations Console: Once Authentication Manager services are restored and the Operations Console is accessible again, SSH can be enabled and disabled through the standard UI method: log in to the Operations Console and navigate to Administration > Operating System Access > Enable SSH Access. This is the recommended method for routine SSH management.