Chat now with support
Chat mit Support

One Identity Safeguard for Privileged Passwords 7.4 - 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 Home page Privileged access requests Appliance Management
Appliance Backup and Retention Certificates Cluster Global Services External Integration Real-Time Reports Safeguard Access Appliance Management Settings
Asset Management
Account Automation Accounts Assets Partitions Discovery Profiles Tags Registered Connectors Custom platforms Importing objects
Security Policy Management
Access Request Activity Account Groups Application to Application Cloud Assistant Asset Groups Entitlements Linked Accounts User Groups Security Policy Settings
User Management Reports Disaster recovery and clusters Administrator permissions Preparing systems for management Troubleshooting Frequently asked questions Appendix A: Safeguard ports Appendix B: SPP and SPS join guidance Appendix C: Regular Expressions

Adding a user

It is the responsibility of either the Authorizer Administrator or the User Administrator to add SPP users.

To add a user

  1. Navigate to User Management > Users.
  2. In Users, click Add from the toolbar.

  3. In the New User dialog, provide information in each of the tabs:

Identity tab (add user)

On the Identity tab, choose an identity provider from the list of available providers. When adding a user from an external identity provider such as Microsoft Active Directory, SPP imports read-only contact information from the source, however, you can change the user photo.

Use valid combinations of identity and authentication providers. For more information, see Identity and Authentication.

Table 226: User: Identity tab properties
Property Description
Identity Provider

The source of the user's identity. SPP comes with a built-in identity provider called Local that will allow you to manually enter user information that is stored directly in SPP. Or you can select an Active Directory or LDAP server that you have previously configured and then browse for a user. SPP will periodically synchronize with the directory to keep the information up to date.

Indicate how the user's identity is managed by SPP:

  • Local
  • Active Directory
  • LDAP
  • Starling
Browse

(Active Directory, Starling, or LDAP)

If the identity provider is Active Directory, Starling, or LDAP, click the Browse button to choose a username. The remaining fields are auto-populated.

Username

(Local provider)

Enter the user's name that displays in the application. This is not the Login name which is set on the Authentication tab (add user).

First Name

(Local provider)

Enter the user's first name.

Limit: 30 characters; no double quotes.

Last Name

(Local provider)

Enter the user's last name.

Limit: 30 characters; no double quotes

Work Phone

(Local provider)

Enter the user's work telephone number.

Limit: 30 characters

Mobile Phone

(Local provider)

Enter the user's mobile telephone number.

Limit: 30 characters

Email

(Local provider)

Enter the user's email address.

Limit: 255 characters

NOTE: Required for approvers using the Cloud Assistant feature and OneLogin MFA as their authentication provider. In addition, OneLogin MFA requires the email address entered in this field be identical to the email address configured in OneLogin.

Description

(Local provider)

Enter information about this user.

Limit: 255 characters.

Time Zone

Select the user's time zone.

Because Microsoft Active Directory does not have a Time Zone attribute, when you add a directory group, the default time zone is set for all imported accounts to (UTC) Coordinated Universal Time. To reset the time zone, open each imported account in Users and modify the Time Zone on this Location tab.

Authentication tab (add user)

On the Authentication tab, specify the authentication settings for the user. An authentication provider can be the same or different as the user's identity provider.

Use valid combinations of identity and authentication providers. For more information, see Identity and Authentication.

Table 227: User: Authentication tab properties
Property Description
Authentication Provider

Indicates how this user is to authenticate to SPP. The options are:

  • Certificate: With a certificate

    NOTE: SPP allows you to map a public-key certificate to a user account. You can then use the certificate to make authenticated requests to the appliance by means of the API. For more information, see Using the API.

  • Local: With a user name and password (default)
  • <Directory name>: With directory account credentials (only available if one or more directories have been added to SPP, such as Active Directory or LDAP, and the identity provider of the user is also that directory).
  • <External Federation service provider name>: With the credentials required by the External Federation or Radius server (only available if one or more of those authentication providers have been configured in SPP).

If Certificate provider:

Certificate, Certificate Thumbprint (SHA-1)

If adding a Certificate user, enter the unique hash value (40 hexadecimal characters) of the certificate. You can copy and paste the Thumbprint value directly from the certificate, including the spaces.

If external federation provider:

Email Address or Name Claim

If adding an external federation user account, enter the email address or name claim that will be returned from the STS of an authenticated user. A case-insensitive comparison will be performed on the value when the user is logging in.

NOTE: You must configure or ensure that the STS includes either the email address claim or name claim. SPP will first look for the email address claim in the claims token. If that claim does not exist, it will use the name claim. You must create the user account in SPP according to what claim is returned by your STS, with precedence given to the email address claim.

If local or Radius as Primary provider:

Login name

If using Local or Radius as Primary for authentication, this is the user's login name. This defaults to the value entered on the Identity tab, Username field.

If using directory authentication, the login name is auto-populated.

Set Password button

(editing an existing Local provider)

If you are editing an existing user for a Local provider, you may click Set Password to change a user's password. This button is not available when creating a new user or editing a user account from an external identity provider like Microsoft Active Directory.

Password

(adding a Local provider)

If adding a Local user, enter a password for the user. You must comply with the password requirements specified in the dialog. For more information, see Local Password Rule.

Require Certificate Authentication

(Active Directory provider if provider is MS AD)

Select this check box to require that the user logs into SPP using their domain issued user certificate or SmartCard. This option is only available when the Authentication Provider is a Microsoft Active Directory.

Password Never Expires

Select this check box to set a password that does not expire.

User must change password at next login

This check box is only available when using Local for authentication. When selected, this check box requires the user to change their password during their next login.

Require Secondary Authentication

Select this check box to require that this user logs in to SPP with two-factor authentication. For more information, see Requiring secondary authentication log in.

Then choose the Secondary Authentication Provider for this user. Use valid combinations of identity and authentication providers. For more information, see Identity and Authentication.

Login Name

(for secondary authentication; not used for FIDO2)
  • When a directory is selected for secondary authentication, Browse to select the account on the secondary authentication provider this user must use when logging into SPP with two-factor authentication.
  • If Radius as a secondary authentication provider is selected, this value is pre-populated with the log in identifier. For more information, see Radius settings.

A best practice is to have the users log in to validate the correct user is set up.

Permissions tab (add user)

On the Permissions tab, select the user's Administrator permissions, if applicable. For details on the rights for the permissions, see Administrator permissions.

Users permissions across multiple user groups

Users have permissions based on the user groups to which they are assigned. If a user is removed from a user group, the permissions related to that group are removed but the permissions for all other groups the user is assigned to remain in place.

User permissions on import

When a directory user group is imported, newly created Safeguard users are assigned the selected permissions. If the user exists in Safeguard, the selected permissions are added to the existing user permissions.For more information, see Adding a directory user group.

To assign permissions

When assigning permissions to a user, select the appropriate access controls. You can Select all or Select none at the bottom of the dialog.

  • Authorizer: Allow the user to grant permissions to other users. This permission allows the user to change their own permissions.

  • User: Allow the user to create new users, unlock and reset passwords for non-administrative users.
  • Help Desk: Allow the user to unlock and set passwords for non-administrative users.
  • Appliance: Allow the user to edit and update the appliance and to configure external integration settings, such as email, SNMP, Syslog, and Ticketing.
  • Operations: Allow the user to reboot and monitor the appliance.
  • Auditor: Allow the user read-only access encompassing all auditor roles. You can limit the Auditor role access by deselecting one of the following check boxes:
    • Application Auditor: Allow the user read-only access to Asset Management and Security Policy Management.
    • System Auditor: Allow the user read-only access to Appliance Management and User Management.
  • Asset: Allow the user to add, edit, and delete partitions, assets, and accounts.
  • Security Policy: Allow the user to add, edit, and delete entitlements and polices that control access to accounts and assets.
  • Personal Passwords: Allow the user to add, edit, delete, share, and access the personal password vault. This check box is only available to the User Administrator and Security Policy Administrator. For more information, see Personal password vault.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen