When you specify an SSH secured session using the spo_ssh, spo_ssh1, or spo_ssh2 protocol, the initial login messages come from the Operations Sentinel services rather than from the managed system, as dictated by the SSH protocol. These messages solicit a username and password. If the managed system uses SSH version 2 and is so configured, messages soliciting a new password are also produced.

The messages are made visible on any replicated screens that are open to that monitoring session and are also available to be matched by SP-AMS, as well written to the log of the corresponding system. Note that none of the responses are logged. Also, if the key Operations Sentinel receives from a managed SSH compatible system does not match the recorded key, a message is displayed indicating the mismatch has occurred. This is a fatal, potentially serious security issue that requires manual intervention. See the Operations Sentinel Administration and Configuration Guide for more information.

The solicitation message for a username is

Username:

The solicitation message for a password is

Password:

When the SSH server (SSH version 2 only) is so configured and is capable of supporting the solicitation for and replacement of a password, the following message appears.

New password:

followed by

New password again:

If the two passwords do not match, the following message appears and there is another opportunity to enter a new password.

New passwords don’t match, try again

As described above, if the host key supplied by the SSH server does not match the key Operations Sentinel has stored for that system, the following message appears:

Host key does not match recorded value,
possible security intrusion!

This should only occur if the SSH server has had its keys regenerated or there is another system that is trying to pass itself off as the target host. See the Operations Sentinel Administration and Configuration Guide for more information.