One Identity Safeguard for Privileged Passwords 7.4.1 - User Guide

If Access Type is RDP, SSH, or Telnet, select this check box to include a password release with session access requests.

If Access Type is RDP, SSH, or Telnet, select this check box to include an SSH Key release with session access requests.

If Access Type is RDP, SSH, or Telnet, select this check box to close sessions that have expired.

Select this check box if the password is to be changed after the user checks it back in. This check box is selected by default.

Select this check box if the SSH key is to be changed after the user checks it back in. This check box is selected by default.

If Access Type is SSH Key, select this check box to require a passphrase for the SSH key.

Select this check box to allow multiple users access to the accounts and assets governed by this policy. Use the next check box to identify how many users can have access at once.

When the Allow simultaneous access option is selected, enter the maximum number of users that can request access at one time.

If Access Type is RDP, RDP Application, SSH, or Telnet, select one of the following options to define the type of account credentials to be used to access any of the assets defined in the policy scope, in addition to the accounts defined in the policy scope when a session is requested:

• None: (Default) The credentials are retrieved from the vault when the session is requested.
• User Supplied: (Only RDP, SSH, or Telnet) The requester user must provide the credentials when the session is requested.
• Linked Account: The requester user's account is linked to a directory account that will be used when the session is requested.

  • Enable scope filtering for linked accounts: When selected, this setting allows you to limit the number of requestable accounts to linked accounts that are also defined in the policy scope.

    NOTE: If the policy scope includes only assets/asset groups and no accounts, then the scope filtering setting has no effect, and the policy is available to all of the linked directory accounts on each scoped policy asset.

• Directory Account: Use the Browse button to select one or more directory accounts to be used when the session is requested.

  If the Directory Account was migrated from an SPP version prior to 2.7, the directory account identifier may be blank, because earlier SPP versions understood only one assignment and version 2.7 results in multiple assignments.

If Access Type is Password Release, select this check box to allow users to request passwords for their respective linked account. Access to each user’s linked account is governed by the other configurations defined in this policy.

Additionally, Enable scope filtering for linked accounts can be selected in order to limit the number of requestable accounts to linked accounts that are also defined in the scope.

Use this drop-down to select a Safeguard for Privileged Sessions connection policy to use with the access request policy.

If Access Type is RDP Application, use the Browse button associated with this field to select the asset configured to connect with the Windows Application Server.

If Access Type is RDP Application, select this checkbox and then click Browse to locate the host account to use. When deselected, you will be prompted for the information when the session is initialized.

If Access Type is RDP Application, this is the display name for the application that was provided when the remote application was published on the Windows application server.

If Access Type is RDP Application, this is the alias name defined when the remote application was published on the Windows application server. Ensure the full alias path is used, including the two vertical bars before the alias name (for example, ||OISGRemoteAppLauncher).

If this option is used, the Use Application Path and Command Line option will not be available.

If Access Type is RDP Application, this option contains the following 2 fields:

• Application Path (path to the remove application): Enter the full path of an application program relative to the Windows host it will be running on.

• Application Command Line (parameters for the remote application): The Application Command Line contains the command line parameters to the application specified in the Application Path. The command line depends on the application. For example, some applications may require a set command line that will include the full path of the remote application along with its command line parameters while other applications may not require a set command line at all.

If this option is used, the Use Application Alias field will not be available.