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

One Identity Safeguard for Privileged Sessions 7.1.1 - Administration Guide

Preface Introduction The concepts of One Identity Safeguard for Privileged Sessions (SPS)
The philosophy of One Identity Safeguard for Privileged Sessions (SPS) Policies Credential Stores Plugin framework Indexing Supported protocols and client applications Modes of operation Connecting to a server through One Identity Safeguard for Privileged Sessions (SPS) Archive and backup concepts Maximizing the scope of auditing IPv6 in One Identity Safeguard for Privileged Sessions (SPS) SSH host keys Authenticating clients using public-key authentication in SSH The gateway authentication process Four-eyes authorization Network interfaces High Availability support in One Identity Safeguard for Privileged Sessions (SPS) Versions and releases of One Identity Safeguard for Privileged Sessions (SPS) Accessing and configuring One Identity Safeguard for Privileged Sessions (SPS)
Cloud deployment considerations The Welcome Wizard and the first login Basic settings
Supported web browsers The structure of the web interface Network settings Configuring date and time System logging, SNMP and e-mail alerts Configuring system monitoring on SPS Data and configuration backups Archiving Cleaning up audit data Using plugins Forwarding data to third-party systems Starling integration
User management and access control
Login settings Managing One Identity Safeguard for Privileged Sessions (SPS) users locally Setting password policies for local users Managing local user groups Managing One Identity Safeguard for Privileged Sessions (SPS) users from an LDAP database Authenticating users to a RADIUS server Authenticating users with X.509 certificates Authenticating users with SAML2 Managing user rights and usergroups Creating rules for restricting access to search audit data Displaying the privileges of users and user groups Listing and searching configuration changes
Managing One Identity Safeguard for Privileged Sessions (SPS)
Controlling One Identity Safeguard for Privileged Sessions (SPS): reboot, shutdown Managing One Identity Safeguard for Privileged Sessions (SPS) clusters Managing a High Availability One Identity Safeguard for Privileged Sessions (SPS) cluster Upgrading One Identity Safeguard for Privileged Sessions (SPS) Managing the One Identity Safeguard for Privileged Sessions (SPS) license Accessing the One Identity Safeguard for Privileged Sessions (SPS) console Sealed mode Out-of-band management of One Identity Safeguard for Privileged Sessions (SPS) Managing the certificates used on One Identity Safeguard for Privileged Sessions (SPS)
General connection settings HTTP-specific settings ICA-specific settings MSSQL-specific settings RDP-specific settings SSH-specific settings Using Sudo with SPS Telnet-specific settings VMware Horizon View connections VNC-specific settings Indexing audit trails Using the Search interface Advanced authentication and authorization techniques Reports The One Identity Safeguard for Privileged Sessions (SPS) REST API One Identity Safeguard for Privileged Sessions (SPS) scenarios Troubleshooting One Identity Safeguard for Privileged Sessions (SPS)
Network troubleshooting Gathering data about system problems Viewing logs on One Identity Safeguard for Privileged Sessions (SPS) Changing log verbosity level of One Identity Safeguard for Privileged Sessions (SPS) Collecting logs and system information for error reporting Collecting logs and system information of the boot process for error reporting Support hotfixes Status history and statistics Troubleshooting a One Identity Safeguard for Privileged Sessions (SPS) cluster Understanding One Identity Safeguard for Privileged Sessions (SPS) RAID status Restoring One Identity Safeguard for Privileged Sessions (SPS) configuration and data VNC is not working with TLS Configuring the IPMI from the BIOS after losing IPMI password Incomplete TSA response received Using UPN usernames in audited SSH connections
Using SPS with SPP Configuring external devices Using SCP with agent-forwarding Security checklist for configuring One Identity Safeguard for Privileged Sessions (SPS) Jumplists for in-product help Configuring SPS to use an LDAP backend Glossary

Saving login credentials for RDP on Windows

You can use automatic RDP login on Windows, but the stored credentials are not trusted by default, and you have to enter the password for each connection. Create the following local policies on the client to allow delegating saved credentials:

  1. Start the Group Policy Editor: run gpedit.msc.

  2. Navigate to Local Computer Policy > Computer Configuration > Administrative Templates > System > Credentials Delegation.

  3. Open the Allow Delegating Saved Credentials with NTLM-only Server Authentication policy.

  1. Click Show and enter TERMSRV/*.

  2. Click Apply.

  1. Open the Allow Delegating Saved Credentials policy.

  1. Click Show and enter TERMSRV/*.

  2. Click Apply.

  1. Open the Allow Delegating Default Credentials with NTLM-only Server Authentication policy.

  1. Click Show and enter TERMSRV/*.

  2. Click Apply.

  1. Open the Allow Delegating Default Credentials policy.

  1. Click Show and enter TERMSRV/*.

  2. Click Apply.

  1. Verify that the Deny Delegating Saved Credentials policy does not contain TERMSRV/* in the list.

  2. Close the Group Policy Editor.

  3. From the command line, issue the gpupdate /force command.

Configuring RemoteApps

Overview

RemoteApps use RDP channels that are denied by default. When configuring RDP connections for RemoteApps on One Identity Safeguard for Privileged Sessions (SPS), create a custom channel policy which enables the following channels:

  • Drawing

  • rail

  • rail_ri

  • rail_wi

Figure 226: RDP Control > Channel Policies — Configuring the required channels for RemoteApps

Prerequisites
  • You must disable the Use advanced RemoteFX graphics for RemoteApp group policy on the RDP server.

    The policy is available at Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Use advanced RemoteFX graphics for RemoteApp.

  • You must have the Remote Desktop (RD) Licensing role installed.

To configure RemoteApps

  1. Navigate to RDP Control > Channel Policies.

  2. Click to create a new channel policy.

  3. Enter the name for the channel policy.

  4. Choose Drawing as the channel type.

  5. Click to add an additional channel type.

  6. Choose Custom as the second channel type.

  7. In Permitted channels, click to add the following channels:

    • rail

    • rail_ri

    • rail_wi

    (You have to click for each channel.)

  8. Click to save the channel policy.

  9. You have created a channel policy for RemoteApps.

    When you configure a connection that uses RemoteApps in RDP Control > Connections, select this channel policy as the Channel policy of the connection.

Configuring the RemoteApp Launcher

The RemoteApp Launcher enables users the access they need to an application without revealing credentials and passwords. By using the RemoteApp Launcher, you can protect shared credentials and limit an end user’s access to an allowed or required application.

Prerequisites
  • SPS version 6.11 or later.

  • Windows Server 2016 or later.

  • An RDP client.

To configure RemoteApp Launcher-specific settings on the SPS side

  1. In SPS, configure a credential store plugin with the get_remote_app_credentials method implemented. This is required for negotiating application credentials with SPS.

    Ensure that you specify the asset parameter. If your SPS is linked to SPP, you must also specify the connection name parameter.

    Example: do_get_remote_app_credentials configuration
    def do_get_remote_app_credentials(self):
        try:
            credential = self._get_credential_for_asset("password", self.remote_app_asset, self.remote_app_account)
            return {"passwords": [credential]}
        except SafeguardException as exc:
            self.logger.error("Error checking out %s for %s@%s: '%s'", "password", self.remote_app_account, self.remote_app_asset, exc)
            return None

    For more information on how to configure a custom credential store plugin, see Creating custom Credential Store plugins.

  2. Optionally, to enable automatic password handling by the RemoteApp Launcher, configure a custom AA plugin.

    By specifying the asset and account name parameters in an AA plugin, the RemoteApp Launcher will not prompt the user for these credentials and will start the configured application without the user having to know any credentials.

    For more information on how to configure a custom AA plugin, see Creating custom Authentication and Authorization plugins.

  3. Configure RemoteApps in SPS.

    For more information, see Configuring RemoteApps.

  4. Configure an RDP connection that uses RemoteApps in RDP Control > Connections and select the created RemoteApps channel policy as the Channel policy of the connection.

To configure RemoteApp Launcher-specific settings on the Windows side

  1. Download the RemoteApp Launcher.

  2. Install Remote Desktop Services (RDS).

  3. Create a RemoteApp program and make the following settings:

    • For the RemoteApp program location, enter the path to your RemoteApp Launcher, for example, C:\Program Files\OneIdentity\RemoteApp Launcher\OI-SG-RemoteApp-Launcher.exe.

    • Specify to always use command-line parameters as shown in the example below: 

      "C:\Program Files\DBeaver\dbeaver.exe" --args "-con user={username}|password={password}|host=localhost|driver=PostgreSQL|database={asset}|name=work|connect=true" --enable-debug

      Table 10: List of parameters
      Parameter Required? Description
      help No Create the help message.
      cmd Yes Specifies the application to launch. Either the path to an executable or command alias.

      args

      Yes

      Specifies the CLI args to pass to <cmd>. It must contain the {username}, {password} and {asset} template options, which will be expanded with the corresponding information.

      use-path

      No

      Specifies whether to look up the cmd argument in the $PATH variable. The default setting is false. When this flag is set to false, you need to specify the full path to the executable.

      enable-debug

      No

      Specifies whether to write debug logs. The default setting is false.

      The logs are available in the C:\Users\<username>\AppData\Roaming\OneIdentity\OI-SG-RemoteApp-Launcher folder.

      The logs are rotated daily and the file name format is oi_sg_rci_<yyyymmdd>.

      The process and the arguments template is defined by the --cmd and --args command line arguments. In the arguments template, the RemoteApp Launcher replaces the {username} {password} and {asset} with data read from the dynamic virtual channel.

      Example: RemoteApp Launcher configuration to start the DBeaver application

      C:> C:\Program Files\OneIdentity\RemoteApp Launcher\OI-SG-RemoteApp-Launcher.exe --cmd "C:\Program Files\DBeaver\dbeaver.exe" --args "-con user={username}|password={password}|host=localhost|driver=PostgreSQL|database={asset}|name=work|connect=true" --enable-debug

  4. Disable the Use advanced RemoteFX graphics for RemoteApp group policy on the RDP server.

    The policy is available at Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Use advanced RemoteFX graphics for RemoteApp.

    You must have the Remote Desktop (RD) Licensing role installed.

Expected result

An end user can open a required application without any credentials by simply starting the RemoteApp Launcher.

Configuring SPS to enable exporting files from audit trails after RDP file transfer through clipboard or disk redirection

In SPS versions 6.2 and later, you can export files from audit trails after RDP file transfer through clipboard.

In SPS versions 6.5 and later, you can export files from audit trails after RDP file transfer through disk redirection too.

NOTE: You can export files from audit trails that were recorded before the SPS versions described above, if the Clipboard or Disk redirect channel was recorded.

To export files from these audit trails, make sure that you have the appropriate version of the Safeguard Desktop Player installed.

For more information on the process in the Safeguard Desktop Player application, see Exporting files from an audit trail.

To configure SPS to enable extracting files from audit trails after RDP file transfer through clipboard or disk redirection

  1. Navigate to RDP Control > Connections and open an existing connection (or create and configure a new connection).
  2. Expand the connection tab, scroll down to the Channel policy drop-down list, and select a channel policy of your choice from the drop-down list options.
  3. Navigate to RDP Control > Channel Policies and open the channel policy that you selected from the Channel policy drop-down list under RDP Control > Connections.
  4. Ensure that the Clipboard or Redirect drop-down list option under Type and the Record audit trail checkbox are both selected.
  5. (Optional) Click to save your configuration.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択