Planning for SSH authentication

RICOH ProcessDirector requires SSH authentication between servers to transfer files during operation and failover.

In a multiple primary servers environment, the lead primary server, alternate primary server, and UI server must communicate using SSH to transfer files. The authentication without a password lets these transfers occur without manual intervention, which is essential for automatic failover.

SSH requirements

Configure SSH authentication between all three servers. Each server must be able to connect to the other two servers without prompting for a password.

Server SSH keys
Lead primary server Alternate primary server, UI server
Alternate primary server Lead primary server, UI server
UI server Lead primary server, alternate primary server

User account

Configure SSH keys using the aiw1 user account. This is the RICOH ProcessDirector service account that runs the application processes. The aiw1 user must exist on all three servers with the same UID and GID.

Required connections

After configuration, verify that the following SSH connections work without password prompts:

  • Lead primary server to alternate primary server
  • Lead primary server to UI server
  • Alternate primary server to lead primary server
  • Alternate primary server to UI server
  • UI server to lead primary server
  • UI server to alternate primary server

In this section:

  1. Configuring SSH authentication between servers
    Create SSH keys to allow RICOH ProcessDirector to move files between servers while it is running and configure the SSH authentication between servers.
Parent topic: Planning for installation