The following describes how to establish a terminal connection (SSH, TELNET, or TN3270) to a server that requires you to enter a ticket ID.
To establish a terminal connection (SSH, TELNET, or TN3270) to a server that requires you to enter a ticket ID
-
Connect to the server.
You have the option to use the ID of the ticket you are working on as part of the username (replace id with the ticket ID):
ssh ticket_id=id@user@server
NOTE: Your plugin may use a different name for the key ticket_id shown in the example. Plugins work with key-value pairs and the names of keys are entirely up to individual plugins.
-
If you did not provide a ticket ID, One Identity Safeguard for Privileged Sessions (SPS) now prompts you to enter it.
-
Authenticate on the server.
-
If the authentication is successful, you can access the server.
The following describes how to establish a Remote Desktop (RDP) connection to a server that requires you to enter a ticket ID.
To establish an RDP connection to a server that requires you to enter a ticket ID
-
Open your Remote Desktop client application.
-
Enter the ticket ID into your Remote Desktop client application into the User name field, before or after the regular content (for example, your username) of the field. You must provide the ticket ID in the following format:
ticket_id~<your-ticket-id>%
Replace <your-ticket-id> with your actual ticket number. For example:
ticket_id~12345%Administrator
NOTE: Your plugin may use a different name for the key ticket_id shown in the example. Plugins work with key-value pairs and the names of keys are entirely up to individual plugins.
To encode additional data, you can use the following special characters:
For example, to add a token ID before your username, use the following format:
domain\token_id~12345%Administrator
Note how domain information is provided. If your server is in a domain, make sure that you specify the domain in this format: putting it in front, followed by a backslash (\).
-
Connect to the server.
-
Authenticate on the server.
-
If the authentication is successful, you can access the server.
On the default log level, One Identity Safeguard for Privileged Sessions (SPS) logs everything that the plugin writes to stdout and stderr. Log message lines are prefixed with the session ID of the proxy, which makes it easier to find correlating messages.
To transfer information between the methods of a plugin (for example, to include data in a log message when the session is closed), you can use a cookie.
If an error occurs while executing the plugin, SPS automatically terminates the session.
NOTE: This error is not visible in the verdict of the session. To find out why the session was terminated, you have to check the logs.
