Recommended Steps for Implementing Jump Technology

When working with Jump Technology, there are a lot of moving parts. Here is a recommended order of implementation to make full use of your software.

  1. Add Jump Item Roles. Jump Item Roles determine how users are allowed to interact with Jump Items. These roles are applied to users by means of individual account settings, group policies, and/or when added to Jump Groups. For more information about Jump Item Roles, see Use Jump Item Roles to Configure Permission Sets for Jump Clients.
  2. Add Jump Policies. Jump Policies are used to control when certain Jump Items can be accessed by implementing schedules, sending email notifications when a Jump Item is accessed, or requiring approval or user entry of a ticket system ID before a Jump Item may be accessed. Jump Policies are applied to Jump Items upon creation and can be modified from the access console. Additionally, Jump Policies can be applied to users when associating a user or group policy with a Jump Group. For more information about Jump Policies, see Create Jump Policies to Control Access to Jump Clients.
  3. Add Jump Groups. A Jump Group is a way to organize Jump Items, granting members varying levels of access to those items. Users are assigned to Jump Groups either individually or by means of group policy. For more information about Jump Groups, see Use Jump Groups to Configure Which Users Can Access Which Jump Clients.
  1. Deploy Jump Items. This step can be performed in several ways.
    1. Deploy Jumpoints. Jump Shortcuts allow you to access Windows systems on an accessible network. If you plan to use Jump Shortcuts on only your local area network, you do not need a Jumpoint. If you plan to use Jump Shortcuts on remote networks, you must install a Jumpoint. Only users who are added to the Jumpoint can use it to access systems on the remote network. Users are assigned to Jumpoints either individually or by means of group policy. For more information on Jumpoints, see Configure and Install a PRA Jumpoint.
    2. Deploy Jump Shortcuts in Bulk. When creating a large number of Jump shortcuts, it may be easier to import them via a spreadsheet than to add them one by one in the access console. From /login > Jump > Jump Shortcuts, download a CSV template for each type of Jump Shortcut you wish to import. Enter the information for the shortcuts, being sure to set the Jump Group and Jump Policy, and then upload the completed CSV files. For more information about mass import of Jump Shortcuts, see Use a Jump Shortcut to Jump to a Remote System.
    3. Deploy Jump Shortcuts One by One. When creating only a few Jump Shortcuts, it may be quicker to deploy them from the access console. In the Jump interface of the access console, click the Create button. Select the type of Jump Shortcut you wish to create, and enter the details, being sure to set the Jump Group and Jump Policy. For more information on deploying Jump Shortcuts from the access console, see Local Jump Shortcuts, Remote Jump Shortcuts, Remote Desktop Protocol Shortcuts, VNC Shortcuts, Shell Jump Shortcuts, Protocol Tunnel Jump Shortcuts, and Use Web Jump to Access Web Services.