-
Title
How to use UPN usernames in audited SSH connections -
Description
When user names are specified in User Principal Name (UPN) format (e-mail address as username) for an SPS-audited SSH connection the connection is unsuccessful. -
Cause
The reason the connection is unsuccessful is the '@' character in the username is getting interpreted by the inband destination selection feature of SPS. When this happens the username is getting stripped from the domain part and the UPN suffix is interpreted as inband target.
For instance using test@ema.il username, the username for the connection will be 'test' and the inband destination is 'ema.il'.
-
Resolution
SPS interprets the last two '@' characters from the connection string, for exampleusername@my-inband-target@SPSTo avoid this behavior Inband destination selection must be used. By specifying the target host explicitly one can prevent SPS to misinterpret the '@' character from UPN usernames.
In the examples below the UPN user name is "test.ema.il", SPS host name is vboxscb5 and inband target is 129.168.56.102.
Inband destination selection setup on SPS SSH Control -> Connections page:
Example 1) Using the above SSH Connection with OpenSSH client:
Example 2) Using the above SSH Connection with Putty SSH client:
Example 3) Using the above connection with WinSCP client:
-
Additional Information