Chatee ahora con Soporte
Chat con el soporte

Password Manager 5.14.3 - Administration Guide (AD LDS Edition)

About Password Manager Getting Started Password Manager Architecture
Password Manager Components and Third-Party Solutions Typical Deployment Scenarios Password Manager in a perimeter network Management Policy Overview Password Policy Overview reCAPTCHA Overview User Enrollment Process Overview Questions and Answers Policy Overview Data Replication Phone-Based Authentication Service Overview Configuring Management Policy
Management Policies
Checklist: Configuring Password Manager Understanding Management Policies Adding or cloning a new Management Policy Configuring Access to the Administration Site Configuring Access to the Password Manager Self-Service Site Configuring Access to the Helpdesk Site Configuring Questions and Answers Policy Workflow overview Custom workflows Custom Activities Password Manager Self-Service Site workflows Helpdesk Workflows User Enforcement Rules
General Settings
General Settings Overview Search and Logon Options Import/Export Configuration Settings Outgoing Mail Servers Diagnostic Logging Scheduled Tasks Web Interface Customization Instance Reinitialization Realm Instances AD LDS Instance Connections Extensibility Features RADIUS Two-Factor Authentication Internal Feedback Customizing help link URL Password Manager components and third-party applications Unregistering users from Password Manager Bulk Force Password Reset Fido2 key management Working with Redistributable Secret Management account Email templates
Upgrading Password Manager Password Policies Enable 2FA for Administrators and Enable 2FA for HelpDesk Users Reporting Accounts Used in Password Manager for AD LDS Appendix B: Open Communication Ports for Password Manager for AD LDS Customization Options Overview Glossary

Authenticate with RADIUS Two-Factor Authentication

Use this activity to configure Password Manager to use a RADIUS server for two-factor authentication.

It uses one-time passwords (OTP) generated by hardware or software tokens for authentication.

You can use RADIUS Two-Factor Authentication to authenticate users before allowing them to reset or change their passwords, to unlock accounts, or manage Questions and Answers profiles.

Before using RADIUS Two-Factor Authentication for authentication, users have to configure it in General Settings tab on the home page of the Administration Site. For more information, see RADIUS Two-Factor Authentication.

Action Activities

This section describes activities that provide core actions of the helpdesk workflows, such as Reset password in AD LDS, Unlock account, and so on.

Reset Password in AD LDS

This is a core activity of the Reset Password workflow. The activity allows helpdesk operators to reset user passwords in AD LDS instances only. If you want to enable helpdesk operators to reset passwords in several systems, configure the Reset password in AD LDS and connected systems activity. For more information on configuring this activity and using One Identity Quick Connect Sync Engine, see Reset Password in AD LDS and Connected Systems.

In this activity you can configure the Enforce password history option. Password history determines the number of unique new passwords that have to be associated with a user account before an old password can be reused.

Before selecting this option, you should consider the following by-design behavior of Password Manager when that the Enforce password history option is enabled:

  • Password Manager uses two slots from the password history every time a password is reset. For example, if the password history value defines that users cannot reuse any of the last 10 passwords, then Password Manager checks only the last five passwords. Therefore, One Identity recommends that you double the password history value. For example, if you want to prevent users from using the last 10 passwords, enter the value 20.

  • Having entered a new password that is not policy compliant, users may end up with a randomly generated password that they do not know.

Reset Password in AD LDS and Connected Systems

Using this activity, you can configure Password Manager to use One Identity Quick Connect to reset passwords in connected systems. If used in conjunction with Quick Connect, Password Manager allows you to enable users and helpdesk operators to manage passwords across a wide variety of connected systems. To be able to integrate Password Manager with Quick Connect, you must have a working knowledge of Quick Connect Sync Engine.

To enable Password Manager to set passwords in connected systems through a Quick Connect server, the account used to access Quick Connect must be a member of the local administrators group on the Quick Connect server.

Before you can configure Password Manager to use a Quick Connect server for cross-platform password synchronization, you must do the following in Quick Connect:

  • Create a connection to the AD LDS instances managed by Password Manager.

  • Create connections to the systems that you want Password Manager to synchronize passwords with.

  • Map users from the managed AD LDS instances to users in the connected systems.

For more information on how to configure Quick Connect to set passwords in connected systems, see the One Identity Quick Connect documentation.

To enable Password Manager for cross-platform password synchronization

  1. Include the Reset password in AD LDS and connected systems activity in a workflow and click the activity to edit its settings.

  2. In the Quick Connect server name text box specify the IP address or the fully qualified domain name of the Quick Connect server.

  3. Select the account to be used to access the Quick Connect server. You can use either Password Manager Service account or specify another account.

    To specify the user name, you can use either a pre-Windows 2000 logon name (such as DomainName\UserName) or a User Principal Name (such as UserName@DomainName.com).

  4. Specify how you want Password Manager to act when the Quick Connect server is unavailable. To do it, select one of the following and click Next:

    • Act as if no Quick Connect server was specified: Helpdesk operators can manage users’ passwords only in AD LDS instances. No warnings are displayed if Quick Connect server is not available.

    • Alert users and allow them to reset passwords only in AD LDS: Helpdesk operators are notified that other connected data sources are temporarily unavailable, and are allowed to continue managing users’ passwords only in AD LDS instances.

    • Do not allow users to reset passwords: Helpdesk operators cannot perform any password management tasks in AD LDS instances and connected data sources, if the Quick Connect server is not available.

  5. From the list of connected systems, select the systems in which you want to manage user passwords. For each selected system, specify the following options and click Next:

    • System alias

    • Reset password in this system independently from AD LDS: Select this option to allow helpdesk operators to reset users’ passwords in a connected system independently from AD LDS. If you select this option, helpdesk operators will be able to enter different passwords for users’ accounts in AD LDS and the connected system.

    • Do not allow resetting password in this system independently from AD LDS: Select this option to prevent helpdesk operators from resetting users’ passwords in a connected system independently from AD LDS. Note, if you select this option, a user’s password will be reset in the connected system only after the password has been successfully reset in AD LDS. If the user’ password is not reset in AD LDS, it will be not reset in the connected system. Helpdesk operators can specify a different password for the connected system, if you select the Allow specifying different password for this system option.

  6. To enforce password history in the AD LDS instances managed by Password Manager, select the Enforce password history check box. Password history determines the number of unique new passwords that have to be associated with a user account before an old password can be reused.

    IMPORTANT: Before selecting this option, you should consider the following by-design behavior of Password Manager when that the Enforce password history option is enabled:

    • Password Manager uses two slots from the password history every time a password is reset. For example, if the password history value defines that users cannot reuse any of the last 10 passwords, then Password Manager checks only the last five passwords. Therefore, it is advised that you double the password history value.

    • Having entered a new password that is not policy compliant, users may end up with a randomly generated password they don't know.

  7. Click OK to close the wizard.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación