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

Password Manager 5.13.1 - 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 Configuring Access to the Administration Site Configuring Access to the Legacy Self-Service Site and Password Manager Self-Service site Configuring Access to the Helpdesk Site Configuring Questions and Answers Policy Workflow overview Custom workflows Custom Activities Legacy Self-Service or 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 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 Feature imparities between the legacy and the new Self-Service Sites Glossary

Password Manager for AD LDS Components

Password Manager for AD LDS includes the following components:

Table 1: Password Manager Components

Component

Description

Importance

Password Manager x64

The suite of role-based sites that expose the functionality of Password Manager to end users.

NOTE: One Identity recommends that you do not install Password Manager on the machine where the Domain Controller (DC) server is installed.

Required

Licensing

The Password Manager license specifies the maximum number of user accounts in the Password Manager across all domains. The Admin can identify whether the installation is legally compliant running the User Status Statistics (USS) tasks, where the scheduler counts the actual number of user accounts, and compares it with the maximum number specified by the license. If a deviation occurs between the actual licenses purchased and the number of users using it, the status of the license changes accordingly in the Admin site indicating whether the installation is compliant or not.

To view the compliance statuses of the license

  1. Login to the Admin site.

  2. On the left pane, click Licensing. The Licenses page appears.

  3. Click the Licenses tab and view the Compliant column.

In the Licenses page, you can view the licensing information of both Password Manager and Telephone Verification, if installed.

The table below provides more information on various compliant status.

Conditions

Status Description

If the total number of users in the user scope exceeds the purchased license or if the license expires

Appears when the license is not compliant.

If the total number of users in the user scope matches with the purchased license or when the user count does not exceed, and the license does not expire

Appears when the license is compliant.

If the total number of users exceeds the purchased license or if the license expires

Appears when the license is not compliant. By clicking this icon, a pop up window appears indicating the reason for not being compliant.

To view the license number, navigate to the About section in the Administration site and click Licenses tab. The License Number appears.

In the event of a license violation, you have the following options

  • Exclude the additional number of user accounts from the user accounts managed by Password Manager to bring your license count in line with the licensed value and run the User Status Statistics(USS) scheduled task in the Administration site to recalculate and display the new user counts.

  • Remove one or more managed domains to decrease the number of managed user accounts.

  • Purchase a new license with a greater number of user accounts, and then update your license using the instructions provided later in this section.

Note that the following items are not limited by the license

  • The number of computers connected to the Administration, Self-Service, and Helpdesk sites of Password Manager.

  • The number of Password Manager instances in a large enterprise. Password Manager can be installed on multiple computers for enhanced performance and fault tolerance.

Installing the License

The license is initially installed when you install the Password Manager:

  1. In the Installation Wizard, click Licenses to display the License status dialog.

  2. Click Browse license, locate and open your license key file using the Select License File dialog, and then click Close.

Some license types may include counters for managed persons and managed external persons along with a counter for user accounts. Managed persons are users that have several accounts; for example, one managed person can have three user accounts. Managed external persons are external or temporary employees. The same license violation policy is applied to managed persons and managed external persons as to user accounts. To specify these user groups, use the corresponding license scopes after you install Password Manager.

NOTE: License scopes are available only if your license includes managed persons and managed external persons.

To add AD LDS instance to the managed persons scope

  1. On the menu bar of the Administration site, click Licensing.

  2. On the Licenses page, click the Managed Persons tab.

  3. On the Scope of Managed Persons page, click Connect to AD LDS instance.

  4. If connections already exist, select a connection from the list. If you want to create a new connection, click Add new connection.

  5. If you selected to create the new connection, in the Connect to AD LDS Instance dialog, configure the following options:

    • In the Server name on which AD LDS instance is installed text box, enter the name of the server to which you want to connect.

    • In the Port number (LDAP or SSL) text box, enter the port number that you specified when installing the AD LDS instance. If you select the Use SSL check box, enter the SSL port number; otherwise, LDAP port number. It is recommended to use SSL in your production environment.

    • In the Application directory partition text box, enter the name of the application directory partition from the AD LDS instance to which you want to connect.

    • In the Application directory partition alias text box, enter the alias for the application directory partition which will be used to address the partition on the Self-Service site.

    • In the Access account section, select Password Manager Service account to have Password Manager access the AD LDS instance using the Password Manager Service account, otherwise, select The following Active Directory account or The following AD LDS account radio button and enter the required user name and password.

    For information on how to prepare the access account, see Configuring Permissions for Access Account.

  6. Click Save.

To specify groups or organization units included in the scope of managed persons

  1. On the menu bar of the Administration site, click Licensing.

  2. On the Licenses page, click the Managed Persons tab.

  3. On the Scope of Managed Persons page, select the domain connection for which you want to specify groups or OUs and click Edit.

  4. Do the following:

    • To specify the groups, click Add under Groups included into the scope of managed persons.

    • To specify the OUs, click Add under Organizational units included into the scope of managed persons.

  5. Click Save.

To specify groups or OUs excluded from the scope of managed persons

  1. On the menu bar of the Administration site, click Licensing.

  2. On the Licenses page, click the Managed Persons tab.

  3. On the Scope of Managed Persons page, select the connection for which you want to specify groups or OUs and click Edit.

  4. Do the following:

    • To specify the groups, click Add under Groups excluded from the scope of managed persons.

    • To specify the OUs, click Add under Organizational units excluded from the scope of managed persons.

  5. Click Save.

You can use the procedures below to specify the scope of managed external persons.

To add AD LDS instance to the managed external persons scope

  1. On the menu bar of the Administration site, click Licensing.

  2. On the Licenses page, click the Managed External Persons tab.

  3. On the Scope of Managed External Persons page, click Connect to AD LDS Instance.

  4. If connections already exist, select a connection from the list. If you want to create a new connection, click Add new connection.

  5. If you selected to create the new connection, in the Connect to AD LDS Instance dialog, configure the following options:

    • In the Server name on which AD LDS instance is installed text box, enter the name of the server to which you want to connect.

    • In the Port number (LDAP or SSL) text box, enter the port number that you specified when installing the AD LDS instance. If you select the Use SSL check box, enter the SSL port number; otherwise, LDAP port number. It is recommended to use SSL in your production environment.

    1. In the Application directory partition text box, enter the name of the application directory partition from the AD LDS instance to which you want to connect.

    2. In the Application directory partition alias text box, enter the alias for the application directory partition which will be used to address the partition on the Self-Service site.

    3. In the Access account section, select Password Manager Service account to have Password Manager access the AD LDS instance using the Password Manager Service account, otherwise, select The following Active Directory account or The following AD LDS account radio button and enter the required user name and password.

    For information on how to prepare the access account, see Configuring Permissions for Access Account.

  6. Click Save.

To specify groups or organization units included in the scope of managed persons

  1. On the menu bar of the Administration site, click Licensing.

  2. On the Licenses page, click the Managed Persons tab.

  3. On the Scope of Managed Persons page, select the domain connection for which you want to specify groups or OUs and click Edit.

  4. Do the following:

    • To specify the groups, click Add under Groups included into the scope of managed persons.

    • To specify the OUs, click Add under Organizational units included into the scope of managed persons.

  5. Click Save.

To specify groups or OUs excluded from the scope of managed persons

  1. On the menu bar of the Administration site, click Licensing.

  2. On the Licenses page, click the Managed External Persons tab.

  3. On the Scope of Managed External Persons page, select the domain connection for which you want to specify groups or OUs and click Edit.

  4. Do the following:

    • To specify the groups, click Add under Groups excluded from the scope of managed external persons.

    • To specify the OUs, click Add under Organizational units excluded from the scope of managed external persons.

  5. Click Save.

Updating the license

If you have purchased a new license, you need to update the license by installing the new license key file. You can use the About section of the Administration site to check the license number that is already installed.

To update the license

  1. On the menu bar of the Administration site, click Licensing.

  2. On the Licenses page, click Install License.

  3. Select the license key file.

  4. Click Save.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択