サポートと今すぐチャット
サポートとのチャット

Safeguard for Privileged Passwords On Demand Hosted - Administration Guide

Introduction System requirements and versions Using API and PowerShell tools Using the virtual appliance and web management console Cloud deployment considerations Setting up Safeguard for Privileged Passwords for the first time Using the web client Getting started with the desktop client Using the desktop client Activity Center Search box Privileged access requests Toolbox Accounts Account Groups Assets
General/Properties tab (asset) Accounts tab (asset) Account Dependencies tab (asset) Owners tab (asset) Access Request Policies tab (asset) Asset Groups tab (asset) Discovered SSH Keys (asset) Discovered Services tab (asset) History tab (asset) Managing assets
Asset Groups Discovery Entitlements Linked Accounts Partitions Profiles Settings
Access Request settings Appliance settings Asset Management settings Tags Backup and Retention settings Certificates settings Cluster settings Enable or Disable Services settings External Integration settings Password Management settings Real-Time Reports Safeguard Access settings SSH Key Management settings Security Policy Settings
Users User Groups Disaster recovery and clusters Administrator permissions Preparing systems for management Troubleshooting Frequently asked questions Appendix A: Safeguard ports Appendix B: SPP 2.7 or later migration guidance Appendix C: SPP and SPS join guidance Appendix D: Regular Expressions About us

Launching the SSH client

Once an SSH session request becomes available, the requester can launch the SSH client to start the session. This is applicable for both the web client and desktop client user interfaces.

To launch the SSH client to begin your session then close your session

  1. If the User Supplied option is selected in the policy, you will be prompted to enter your user credentials. After entering the requested credentials, click Apply. This will retrieve the information (for example, Hostname Connection String) required to launch the SSH client.

  2. Click the Launch/Start SSH Session button associated with the asset name.

    NOTE: The Launch/Start SSH Session options are available only if enabled by user preferences.

    • In the web client, a session will launch if you have an application registered (ssh:// for SSH protocol).

    • In the desktop client, clicking Launch displays the PuTTY Configuration dialog. The required information is populated, click Open to launch the SSH client. If the required information is not populated in the PuTTY Configuration dialog, use the following buttons to copy and paste the information into the dialog:

      • Use the buttons to the right of the Hostname Connection String to perform the following tasks:

        • View: To view the hostname connection string.

        • Copy: To copy the value to your copy buffer, which can then be pasted into the Hostname field of the PuTTY Configuration dialog.

        • Help: To copy the value into the Hostname field of the PuTTY Configuration dialog.

      • Use the buttons to the right of the Password or SSH Key to perform the following tasks.

        • View: To view the password or SSH key.

        • Copy: To copy the password or SSH key to your copy buffer, which can then be pasted into the Password or SSH Key field of the PuTTY Configuration dialog.

        • Help: To copy the value into the Password or SSH Key field of the PuTTY Configuration dialog.

        • NOTE: The Password or SSH Key field only appears if the Include password release with session requests option (Access Config tab) is selected in the entitlement's access request policy.

  3. In the SSH client, run the commands or programs on the target host.

    If there is no activity in an open session for about 10 minutes, the session will be closed. However, as long as the request is in an Available state, you can launch the session again to resume your tasks.

  4. Once you are completed, log out of the target host and select Check in to complete the session request process.

    This makes the session request available to reviewers. If the Record Sessions option is enabled in the policy, the reviewer can play back the recording as part of the review process. In addition, if the Enable Command Detection option is selected in the policy, the reviewer can view a list of the commands and programs run during the session.

Launching an RDP session

Once an RDP session request becomes available, the requester can launch the remote desktop connection to start the session. This is applicable for both the web client and desktop client user interfaces.

To launch a remote desktop connection

  1. If the User Supplied option is selected in the policy, you will be prompted to enter your user credentials. After entering the requested credentials, click Apply. This will retrieve the information (for example, Username Connection String) required to launch the remote desktop session.

  2. Depending on your interface:

    • (web client) In the web client:

      NOTE: The Start RDP Session option is available only if enabled by user preferences.

      • If you have an application registered (rdp:// for RDP sessions), you can click the Start RDP Session button associated with the asset name then click Connect. See KB 313918 for details on application registration. A password must be entered and we recommend sg. A blank password will cause the session to fail.
      • If you do not have an application registered, download the RDP launch file instead of using the Start RDP Session button. A password must be entered and we recommend sg. A blank password will cause the session to fail.
    • (desktop client) Click the Launch button to the right of the asset name. Clicking this button displays the Remote Desktop Connection dialog. Click Connect to launch the remote desktop session.

    NOTE: If the required information is not populated in the Remote Desktop Connection dialog, use the following buttons to copy and paste the information into the dialog:

    1. Use the buttons to the right of the Username Connection String to perform the following tasks:

      • View: To view the username connection string.
      • Copy: To copy the value to your copy buffer, which can then be pasted into the Username field of the Remote Desktop Connection dialog.
      • Help: To copy the value into the Username field of the Remote Desktop Connection dialog.

    2. Use the buttons to the right of the Password or SSH Key to perform the following tasks:

      • View: To view the password or SSH key.
      • Copy: To copy the password or SSH key to your copy buffer, which can then be pasted into the Password or SSH Key field of the Remote Desktop Connection dialog.

      • Help: To copy the value into the Password or SSH Key field of the Remote Desktop Connection dialog.

      NOTE: The Password or SSH Key field only appears if the Include password or SSH key release with session requests option (Access Config tab) is selected in the entitlement's access request policy. For more information, see Access Config tab (create access request policy desktop client).

Begin your RDP session and close the session

  1. In the remote desktop session, run the commands or programs on the target host.
    If there is no activity in an open session for about 10 minutes, the session will be closed. However, as long as the request is in an Available state, you can launch the session again to resume your tasks.

  2. Once you are completed, log out of the target host and select Check in to complete the session request process.

    This makes the session request available to reviewers. If the Record Sessions option is enabled in the policy, the reviewer can play back the recording as part of the review process. In addition, if the Enable Window Title Detection option is selected in the policy, the reviewer can view a list of the windows opened on the desktop during the session.

Configuring and launching a Remote Desktop Application session

In order to launch a remote desktop application session request, some additional configuration is required.

To configure and launch a remote desktop application

  1. Install and configure Safeguard for Privileged Sessions's RemoteApp launcher available starting with 6.12. For more information, see One Identity Safeguard for Privileged Sessions Administration Guide.

  2. Publish the OISGRemoteAppLauncher application following Microsoft's instructions. All remote applications that will be launched using SPP/SPS need to be configured to launch with the OISGRemoteAppLauncher and include a command line which references the intended remote application. Take note of the RemoteApp Program Name and Alias since they will be needed when configuring the access request policy.

  3. On Asset Management | Assets, you need the following assets (for more information, see Adding an asset (web client)):

    1. Windows Server asset: This asset will be used to connect with a Windows Application Server.

    2. Other/Other Managed asset: This asset (of either platform type) is used to connect with the remote application. It requires the following settings:

      • Network Address: None

      • Authentication Type: None

      • An account from the remote application added to the Accounts tab.

  4. On Security Policy Management | Entitlements, you will need an entitlement containing a Remote Desktop Application access request policy. For more information, see Creating an access request policy (web client).

  5. Within Safeguard for Privileged Sessions, a channel policy needs to be modified or created to include the following attributes. This channel policy will also need to be referenced from an RDP connection policy. For more information, see One Identity Safeguard for Privileged Sessions Administration Guide.

    1. In RDP Control | Connections, set the Channel policy to applications.

    2. In RDP Control | Channel Policies, create the following:

      1. Dynamic virtual channel: No configured settings.

      2. Custom: Add the following to Permitted channels:

        • rail

        • rail_ri

        • rail_wi

Once a remote desktop application session request becomes available, the requester can launch the remote desktop connection to start the session.

To launch a remote desktop application connection

In the web client: Click the Start RDP Session button associated with the asset.

NOTE: The Start RDP Session option is available only if enabled by user preferences and if you have installed Session Client Application Launch Uri System (for more information, see SCALUS).

NOTE: A black window may appear on the screen as the launcher loads the remote desktop application session.

Reviewing a session request

The Security Policy Administrator can configure an access request policy to require a review of completed session requests for assets or accounts in the scope of the policy.

NOTE: You can configure Safeguard for Privileged Passwords to notify you of an access request that requires your review. For more information, see Configuring alerts.

Desktop Player User Guide

To download the player user guide, go to One Identity Safeguard for Privileged Sessions - Technical Documentation. Scroll to User Guide and click One Identity Safeguard for Privileged Sessions [version] Safeguard Desktop Player User Guide.

(web client) To review a completed sessions request

Select Reviews on the left of the page to manage reviews. On the Reviews page, you can:

  • View details by selecting a request then looking at the details display on the right of the page, including the workflow.
  • Mark one or more request as reviewed: Select the requests. Do the following:
    • If no comment is needed, click Mark all the selected requests as reviewed.
    • If a comment is needed, this icon will display as One or more of the selected requests requires review comments. Add the comment. Then, click Mark as Reviewed.
  • Change the columns that display: Click Select columns to display then select the columns you want to see.
    • Action: Displays This request requires review comments or Mark only this request as reviewed.
    • Requester: Displays the user name of the requester.
    • Access Type: Displays the type of access (for example, Password, SSH Key, RDP, SSH, or Telnet).
    • Account: Displays the managed account name.
    • Ticket Number: Displays the ticket number, if required.
    • Request For/Duration: Displays the date and time as well as the window of availability (for example, March 20, 2021 9:56 AM 2 hours).
  • Search: For more information, see Search box.

(desktop client) To review a completed sessions request

  1. From your  Home page, the Reviews widget has these controls:
    1. Click  (expand down) to open the list of pending reviews.
    2. Click  Popout to float the Reviews pane.

      You can then select and drag the pane to any location on the console and resize the window.

    NOTE: You enable or disable the Home page widgets in the  Settings (desktop client) menu.

  2. Open the list of pending reviews and select an account name to see the details of the sessions request.

  3. Take the following action on sessions requests:

    1. Select Workflow to review the transactions that took place in the selected request.

      • If Record Sessions is enabled in the policy, click Play on the Initialize Session event to play back the session.

        A (green dot) indicates the session is live. A user with Security Policy Administrator permissions can click this icon to follow an active session.

        If the session recording has been archived from the local Safeguard file system or was recorded prior to linking a Sessions Appliance, you will see a Download button instead of a Play button. Click Download to download the recording and then click Play.

        CAUTION: If you receive a message like: No Desktop Player. The Safeguard Desktop Player is not installed. Would you like to install it now?, click Yes. See Installing the desktop client, Installing the Desktop Player, step 2.

      • If Enable Command Detection is enabled in the policy, expand to show the details and click the events link on the Initialize Session event to view a list of the commands and programs run during the session.

        For an RDP session, the setting is Enable Windows Title Detection. When enabled, you can view a list of windows that were opened during the privileged session.

    2. Select  Review to complete the review process.

      Optionally, enter a comment of up to 255 characters.

    Once the review is complete, it no longer appears on the Reviews pane.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択