If you are designated as an authorized user of an entitlement, you can request access for a specific period (or session) to any account or asset in the scope of the entitlement's policies.

You can configure Safeguard for Privileged Passwords to notify you of pending access request workflow events, such as when a session request is pending, denied, or revoked, and so on. For more information, see Configuring alerts.

To request session access

1. Click Home then New Request or open My Requests then click New Request.

   NOTE: You can also submit an access request from your Favorites pane, if you previously saved it as a favorite.

2. On the New Access Request page, select the accounts to be included in the access request and the type of access being requested for each selected account. You can search for accounts based on asset information. The assets available for selection are based on the scope defined in the entitlement's access request policies.

   If an SPS_Initiated connection policy is selected when creating an access request, the assets associated by that request will not display. The session-related access policy assigned to SPS_Initiated is filtered out. A connection policy other that SPS_Initiated must be selected to create an Access Request for the asset.

   NOTE: Use the button to select the columns to display.

   • Asset: The display name of the managed system.

   • Account: The available account appears in the Account column. When an asset has multiple accounts available, either Select Account(s) or the account name appears as a hyperlink in the Account column. Click the hyperlink in the Account column to display a list of accounts available and select the accounts to be included in the access request.

     If Show Account Availability is enabled you can identify if a privileged account is available or not. Accounts display a warning badge if in use by a request. An account's status is updated immediately after being changed in order to avoid overlapping account requests from multiple users. Hover over the badge to display <X> of <X> accounts in use. Showing account availability requires additional API queries that may impact performance. This toggle is set by the user not an administrator. There is no global toggle.

     NOTE: When the policy governing the request has enabled Allow simultaneous access for multiple user access, the request may still be available even though Show Account Request Availability indicates it is in use.

   • Access Type: The type of access request appears in the Access Type column. If the type is a drop-down, multiple access request types are available. Select the hyperlink and select the access type.

   • Account Description: (When applicable) The description of the account.

   • Asset Description: (When applicable) The description of the asset.

   You can remove an asset or account from the list by clearing the check box associated with an entry in the grid.

3. Click Next.

4. On Request Details, configure the following settings, which will apply to all of the selected assets and accounts:

   1. Emergency Access: If the policy has emergency access enabled, select this option to gain immediate emergency access to this password. When you use Emergency Access, the request requires no approval. For more information, see Creating an access request policy.

   2. When: Select one of the following options:

      1. Now: If selected, the request is immediately created.

      2. Later: If selected, fields will appear allowing you to enter a specific date and time for the request in the user's local time.

   3. How Long: Based on the policy, do one of the following:
      • View the Checkout Duration.
      • If the Allow Requester to Change Duration option is enabled in the policy, you can set the days, hours, and minutes that you want to use the password. This overrides the Checkout Duration set in the access request policy. For more information, see Creating an access request policy.

   4. Ticket Number: If the policy requires a ticket number, enter a ticket number. If multiple accounts are in the request and one or more require a ticket number, the ticket number is applied to all of the requests associated with this access request. For more information, see Ticket systems.

   5. Reason: If the policy requires a reason, enter a reason. If multiple accounts are in the request and one or more require a reason. The reason is applied to all of the requests associated with this access request. For more information, see Reasons.

      Select the Description down arrow to view the description defined for the selected reason.
      
      

   6. Comment: If required, enter information about this request. When multiple accounts are specified in the request, if any of the selected accounts require a comment, you must enter a comment. The comment will be applied to all of the requests associated with this access request. The limit is 255 characters.

5. To save the access request as a favorite, select the Save this request as a favorite check box and enter a name for the request.

   This access request is then added to your Favorites. In the web client, favorites are displayed on the Home page and the My Requests page.

6. After entering the required information, click Submit Request.

   Additional information displays if the access requests submitted were unsuccessful with information on how to address the issues. Once they have been addressed, you can resubmit the request.
   

When the request has been approved, you can use the password. For more information, see Taking action on a password release request.

If the session does not launch

In a rare event that the access request does not result in a launchable session request, the following notifications display:

• Please try again. The linked sessions module state is currently down or may be in a locked state. This message may mean one of the following:
  • Safeguard for Privileged Passwords could not contact Safeguard for Privileged Sessions. Try again so the request can be redirected to another managed host in the Safeguard for Privileged Sessions cluster.

  • The Safeguard for Privileged Sessions configuration is locked. Try again because this condition is typically because the Safeguard for Privileged Sessions administrator is making configuration changes to the Safeguard for Privileged Sessions appliance at the same time that a new access request is being created or a session is being launched.

• Missing the session connection policy. or
  The selected Access Request Policy cannot be used to initiate a session from SPP. The highest priority policy must be associated with a valid SPS connection policy.
  Check the connection policy configuration. In the web client, go to Security Policy Management > Entitlements > (edit) > Access Request Policies to add a valid connection policy. Save the policy and recreate the access request.