立即与支持人员聊天
与支持团队交流

One Identity Safeguard for Privileged Sessions 6.5.0 - Administration Guide

Preface Introduction The concepts of One Identity Safeguard for Privileged Sessions (SPS) The Welcome Wizard and the first login Basic settings
Supported web browsers and operating systems 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 and cleanup Forwarding data to third-party systems Joining to One Identity Starling
User management and access control Managing One Identity Safeguard for Privileged Sessions (SPS)
Controlling One Identity Safeguard for Privileged Sessions (SPS): reboot, shutdown Managing 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 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) RPC API 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) 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

Active Directory LDAP backend

In addition to the common parameters, the Active Directory (AD) backend has the following additional configurable parameters:

  • membership_check: Enable AD group membership check enables AD specific non-primary group membership checking.

    NOTE:

    The AD user’s primary group is always checked regardless of this setting.

    • nested_groups: Enable nested groups allows AD nested group support. See below for details.

Additionally, AD supports case and accent insensitive matching in many of the user and group name attributes. Since SPS relies on the server to perform comparisons, case and accent insensitive user and group name support depends solely on the server configuration.

User identification in AD

To determine the user entry for a given plain username, SPS performs a search under user_base_dn for objects having either the sAMAccountName or the userPrincipalName equal to the plain username of the user. The objectClass of the user object is not restricted.

NOTE:

Although userPrincipalName in AD is a Internet-style name like user@example.com, it matches simple names like user.

Only the user object returned here is used for group membership checks.

Group membership resolution in AD

For all group membership checks, only the LDAP user object returned during user identification phase is used.

The plain group name is always compared to the cn attribute of the group object.

A user is treated as a member of a group if both the group object’s objectClass and objectCategory is group, and any of the following is true:

  • The group is the user’s primary group. That is, the objectSID attribute of the group matches the Security Identifier calculated from the user object’s objectSID and primaryGroupID attributes, as described in the Microsoft Support article How to use the PrimaryGroupID attribute to find the primary group for a user.

    NOTE:

    When using the AD backend, this check is always performed, even if the membership_check option is disabled. However, it is OK for the user to have no primary group.

  • The group lists the user’s short username. That is, the group’s memberUid attribute contains the short username from the user object.

    This check is performed only when the membership_check option is enabled for AD.

    NOTE:

    For the purpose of this check, the user’s short username is retrieved from the user object’s sAMAccountName attribute only, which is a single-valued attribute in AD. This is a known limitation.

    It is OK for the sAMAccountName attribute to be missing, in which case this check will be skipped.

  • The group lists the user’s dn. That is, the group object’s member attribute contains the user’s dn.

    This check is performed only when the membership_check option is enabled for AD.

    This is the only place where nested groups are supported. When the nested_groups setting is enabled in the configuration, SPS will also find groups which do not directly contain the user’s dn in their member attribute, but do contain an intermediate group’s dn, which in turn contains the user dn in its member attribute. This nesting can be arbitrarily deep, limited only by AD.

    NOTE:

    Due to the nature of the way AD resolves the nested group chain, intermediate groups might be outside the configured group_base_dn.

NOTE:

Although an objectCategory in AD is a DN-valued attribute, it does match simple names like group.

Additionally, a user is treated as a member of a group if:

  • The group lists the user’s dn in any of the additional group objects configured in user_dn_in_groups.

    For example, if a row is added with objectClass set to groupOfNames and attribute set to member, SPS will treat the user as a member of all groups where the group is a groupOfNames, and the group’s member attribute contains the user’s dn.

    NOTE:

    There is no additional restriction on the group’s objectClass in this case.

  • The user lists the group’s dn. That is, the user’s memberof_user_attribute contains the dn of the group, and the objectClass of the referred group is group.

    This check is performed only when the memberof_check option is enabled for AD.

    NOTE:

    SPS compares the dn stored in the memberof_user_attribute to the dn of the group object itself in a strict stringwise manner. Therefore, this user attribute must contain the group DN exactly as it would be returned by the LDAP server. No case or accent differences are allowed.

POSIX LDAP backend

In addition to the common parameters, the POSIX backend has the following configurable parameters:

  • username_attribute: Username (user ID) attribute name is the name of the attribute in the user object, which contains the user’s plain username.

  • membership_check: Enable POSIX group membership check enables POSIX primary and supplementary group membership checking. When enabled, it has the following configurable parameter:

    • member_uid_attribute: the optional POSIX group membership attribute name is the name of the attribute in a posixGroup group object, which lists the plain usernames that are members of the group. These groups are usually referred to as supplementary groups of the referred user.

User identification in POSIX

To determine the user entry for a given plain username, SPS performs a search under user_base_dn for objects having the username_attribute equal to the plain username of the user. The objectClass of the user object is not restricted.

The user object returned here is used for group membership checks.

Group membership resolution in POSIX

For all group membership checks, only the LDAP user object returned during user identification phase is used.

The plain group name is always compared to the cn attribute of the group object.

A user is treated as a member of a group given by its plain group name if the plain group name matches the cn attribute of the group object, and any of the following is true:

  • The group is the user’s primary group. That is, the group is a posixGroup, and the user’s gidNumber attribute is equal to the group’s gidNumber attribute.

    This check is performed only when the membership_check option is enabled for POSIX.

    NOTE:

    It is OK for the user to have no gidNumber attribute, in which case this check will be skipped.

  • The group lists the user’s short username. That is, the group is a posixGroup, and it’s member_uid_attribute contains the short username from the user object.

    This check is performed only when the membership_check option is enabled, and the member_uid_attribute is configured.

    NOTE:

    For the purpose of this check, the user’s short username is retrieved from the user object’s username_attribute. Currently, this attribute should only contain a single username. A warning will appear in the logs if this is not the case, and the first value of the attribute will be used as returned by the server. This is a known limitation.

  • The group lists the user’s dn in any of the additional group objects configured in user_dn_in_groups.

    For example, if a row is added with objectClass set to groupOfNames and attribute set to member, SPS will treat the user as a member of all groups where the group is a groupOfNames, and the group’s member attribute contains the user’s dn.

  • The user lists the group’s dn. That is, the user’s memberof_user_attribute contains the dn of the group, and the objectClass of the referred group is memberof_group_objectclass.

    This check is performed only when the memberof_check option is enabled for POSIX.

    NOTE:

    SPS compares the dn stored in the memberof_user_attribute to the dn of the group object itself in a strict stringwise manner. Therefore, the user attribute must contain the group DN exactly as it would be returned by the LDAP server. No case or accent differences are allowed.

Authenticating users to a RADIUS server

One Identity Safeguard for Privileged Sessions (SPS) can authenticate its users to an external RADIUS server. Group memberships of the users must be managed either locally on SPS or in an LDAP database.

Caution:

The challenge/response authentication method is currently not supported. Other authentication methods (for example password, SecureID) should work.

To authenticate SPS users to a RADIUS server

  1. Navigate to Users & Access Control > Settings.

    Figure 72: Configuring RADIUS authentication

  2. Set the Authentication method field to RADIUS.

    The status information displayed ([NOT CONFIGURED] and [CONFIGURED]) indicates whether or not you have provided the shared secret required to access the RADIUS server.

  3. Enter the IP address or domain name of the RADIUS server into the Address field.

    Use an IPv4 address.

  4. Click Change, and enter the password that SPS can use to access the server into the Shared secret field.

    NOTE:

    One Identity Safeguard for Privileged Sessions (SPS) accepts passwords that are not longer than 150 characters. Unicode characters as well as the following special characters can be used: !"#$%&'()*+,-./:;<=>?@[\]^-`{|}

    Click Update.

  5. To use the Password Authentication Protocol, select PAP. To use the Challenge-Handshake Authentication Protocol, select CHAP.

  6. To add more RADIUS servers, click and repeat Steps 2-4.

    Repeat this step to add multiple servers. If a server is unreachable, SPS will try to connect to the next server in the list in failover fashion.

  7. When configuring RADIUS authentication with locally managed user accounts, complete the following steps.

    1. Set Password expiration to 0.

    2. Set Number of passwords to remember to 0.

    3. Set Minimal password strength to disabled.

    4. Set Cracklib check on password to disabled.

  8. Click Commit.

    Caution:

    After you commit this configuration, the SPS web interface will be available only after successfully authenticating to the RADIUS server. Note that the default admin account of SPS will be able to login normally, even if the RADIUS server is unaccessible.

Authenticating users with X.509 certificates

One Identity Safeguard for Privileged Sessions (SPS) provides a method to authenticate the users of the web interface with X.509 client certificates. The client certificate is validated against a CA list, and the username is exported from the client certificate for identification. One Identity recommends using 2048-bit RSA keys (or stronger).

To authenticate SPS users on the SPS web interface with X.509 client certificates, complete the following steps.

Prerequisites
  • You will have to upload the CA certificates that issued the certificates of the users, so this CA certificate must be available on your computer in PEM format.

  • The certificates of the users must contain the username used to authenticate on SPS. You must know which certificate field will contain the usernames (for example, CN or UID).

  • The certificates must be imported into the browsers of the users. SPS offers the possibility to authenticate with a certificate only if a personal certificate is available in the browser.

Figure 73: Policies > Trusted CA Lists — Creating Trusted CA lists

To authenticate users with X.509 certificates

  1. Navigate to Policies > Trusted CA Lists and create a Trusted CA List.

  2. If the user certificates contain the username in the Common Name field, make sure that the Strict Hostname Check is disabled.

  3. Upload the CA certificate.

  4. Adjust other settings as needed. For details on creating a trusted CA list, see Verifying certificates with Certificate Authorities.

  5. Click Commit.

  6. Navigate to Users & Access Control > Settings > Authentication settings.

    Figure 74: Users & Access Control > Settings > Authentication settings — Configuring X.509 authentication

  7. Select X.509.

  8. Select the trusted CA list created in the first step in Authentication CA.

  9. Select which field of the user certificate contains the username in the Parse username from field. In most cases, it is the commonName or userid field, but SPS supports the emailAddress and userPrincipalName fields as well.

  10. To allow the admin user to be able to log in without using X.509 authorization, select Enable fallback for admin. This will fallback to password authentication.

  11. Click Commit.

相关文档