One Identity Safeguard for Privileged Sessions 6.0.7 - Administration Guide

Integrating ticketing systems

The plugin framework provided by One Identity Safeguard for Privileged Sessions (SPS) can also be used to integrate SPS to external ticketing (or issue tracking) systems, allowing you to request a ticket ID from the user before authenticating on the target server. That way, SPS can verify that the user has a valid reason to access the server — and optionally terminate the connection if he does not. Requesting a ticket ID currently supports the following protocols:

• Remote Desktop (RDP)

• Secure Shell (SSH)

• TELNET

• TN3270

• To request a plugin that interoperates with your ticketing system, contact our Support Team.

• For details on configuring SPS to use a plugin, see "Using a custom Authentication and Authorization plugin to authenticate on the target hosts" in the Administration Guide.

Performing authentication with ticketing integration in terminal connections

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

1. 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.

2. If you did not provide a ticket ID, One Identity Safeguard for Privileged Sessions (SPS) now prompts you to enter it.

3. Authenticate on the server.

4. If the authentication is successful, you can access the server.

Performing authentication with ticketing integration in Remote Desktop connections

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

1. Open your Remote Desktop client application.

2. 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:

   • % as a field separator

   • ~ as the equal sign

   • ^ as a colon (for example, to specify the port number or an IPv6 IP address)

   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 (\).

3. Connect to the server.

4. Authenticate on the server.

5. If the authentication is successful, you can access the server.

Creating a custom plugin