Chat now with support
Chat mit Support

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

Enabling HTTPS

We strongly recommend that you use HTTPS with Password Manager. The secure hypertext transfer protocol (HTTPS) is a communications protocol designed to transfer encrypted information between computers over the World Wide Web.

For instructions on how to configure SSL in order to support HTTPS connections from client applications, see Configuring Secure Sockets Layer in IIS 7 in the Microsoft Windows Server 2008 R2 and Windows Server 2008 documentation.

NOTE: To enable the Password Manager installation to be redirected from HTTP to use HTTPS by default, the HSTS (web security policy mechanism) functionality must be enabled. To enable HSTS in Password Manager, in the HKEY_LOCAL_MACHINE\SOFTWARE\One Identity\Password Manager registry key, set the registry value of the HSTSEnabled string to true.

Installing Password Manager

For an overview of various installation scenarios, see Typical Deployment Scenarios.

To install Password Manager

  1. Depending on the hardware, run Password Manager x86 or Password Manager x64 from the installation media autorun window.

  2. Read the license agreement, select I accept the terms in the license agreement, then click Next.

  3. On the User Information page, specify the following options, then click Next:

    1. Full name: Enter your name

    2. Organization: Enter the name of your organization

    3. Licenses: Click Licenses and specify the path to the license file

    NOTE: A license file is a file with the .asc extension that you have obtained from your One Identity representative.

  4. On the Custom Setup page, select the components to install, and then click Next:

    1. Full Installation: Select this option to install the Password Manager Service and the Administration, Self-Service and Helpdesk sites on this computer.

    2. Legacy Self-Service Site: Select this option to install only the legacy Self-Service site.

    3. Password Manager Self-Service Site: Select this option to install only the Password Manager Self-Service site.

    4. Helpdesk Site: Select this option to install only the Helpdesk site.

    You can install all Password Manager components together on a single server or you can deploy the Legacy Self-Service, Password Manager Self-Service, and Helpdesk sites on a standalone server. For mor information about installing the Self-Service and Helpdesk sites on a standalone server, see Installing Legacy Self-Service, Password Manager Self-Service, and Helpdesk Sites on a Standalone Server.

    NOTE: By default Secure Password Extension uses the Self-Service site that is installed on the same server with the Password Manager Service. If you want Secure Password Extension to use another Self-Service site. For more information, see Locating Self-Service Site.

  5. On the Password Manager Service Account Information page, specify the name and password for the Password Manager Service account, and then click Next. Use the following user name format: DOMAIN\Username. For more information on the requirements for the Password Manager Service account, see Configuring Password Manager Service Account and Application Pool Identity.

  6. On the Specify Web Site and Application Pool Identity page, select the website name, specify the name and password for the account to be used as application pool identity, and then click Next. For more information on the requirements for the application pool identity, see Configuring Password Manager Service Account and Application Pool Identity.

  7. Click Install.

    When the installation is complete, click Finish.

    NOTE: By default, Password Manager uses built-in certificates to encrypt traffic between Password Manager websites and Password Manager Service. After installing Password Manager, if the Web sites (Self-Service and Helpdesk) and the Password Manager Service are installed on different computers, it is recommended to replace these certificates with new ones. For more information, see Specifying Custom Certificates for Authentication and Traffic Encryption Between Password Manager Service and Web Sites.

Extending AD LDS Schema

To use Password Manager with an AD LDS instance, you need to extend the AD LDS schema to include required object class definitions.

When installing a unique AD LDS instance, you must specify the LDAP and SSL port numbers and the application directory partition name. Make sure, you remember the values you enter because you will need to use them when extending the AD LDS schema.

IMPORTANT: When you install an AD LDS instance, in the AD LDS setup wizard select the option to create a new application directory partition and, on the Importing LDIF Files page, select all shown files.

To extend AD LDS schema

  1. On a computer where an AD LDS instance is installed, create a temporary folder.

  2. Copy all files from the Password Manager\Setup\ADLDS Extension folder on the Password Manager installation media to the folder you created in step 1.

  3. In the temporary folder, modify the prepare_ad_lds.cmd file using any text editor. Replace the port number in the line SET PORT=50000 with the LDAP port number you specified in the AD LDS setup wizard.

  4. In the temporary folder, modify the data.ldf file using any text editor. Replace all occurrences of the O=Quest,C=US with the application directory partition name you specified in the AD LDS setup wizard.

  5. Run the prepare_ad_lds.cmd file.

Initializing instance

After installing Password Manager on your computer, you need to initialize an instance before you begin to configure a new Management Policy: that is, before configuring the user and Helpdesk scopes, Questions and Answers policy, and managing workflows. When initializing a Password Manager instance, you can choose one of the two options: Create a unique instance or a replica of an existing instance. When you create a replica of the existing instance, the new instance shares its entire configuration with the existing instance. Password Manager instances sharing the same configuration are referred to as a Password Manager realm. For more information about Password Manager realms, see Installing multiple instances of Password Manager.

To initialize Password Manager instance

  1. Open the Administration site by entering the following address: http(s)://<ComputerName>/PMAdmin, where <ComputerName> is the name of the computer on which Password Manager is installed. You can obtain the URL path to the Admin site from your system administrator. On the logon page, enter your user name and password and click Log on. The Instance Initialization page will be displayed automatically.

    NOTE: For Password Manager versions 5.8.x or later, users must be a part of the local PMAdmin group and either of IIS_IUSRS or Administrators group to access the PMAdmin site.

  2. On the Instance Initialization page, select one of the following options, depending on what type of instance you want to create.

    • Unique instance: Creates a new instance.

    • Replica of existing instance: Joins a new instance to a Password Manager realm.

  3. If you have selected the option Replica of an existing instance, follow the instructions provided later in Installing multiple instances of Password Manager.

  4. If you have selected the option Unique instance, under Service connection settings, specify the following:

    • Certificate name: Select the certificate that was issued for the computer running the Password Manager Service. If you decide to install the Legacy Self-Service, Password Manager Self-Service, and Helpdesk sites separately from the Password Manager Service, it is recommended to replace the built-in certificate that is used encrypt traffic between the Service and the sites. For more information, see Specifying Custom Certificates for Authentication and Traffic Encryption Between Password Manager Service and Web Sites.

    • Port number: Specify the port that the Self-Service and Helpdesk sites will use to connect to the Password Manager Service. By default, port 8081 is used.

  5. Under Advanced settings, specifying the following:

    1. Encryption algorithm: Specify the encryption algorithm that will be used to encrypt users’ answers to secret questions and other security sensitive information. You can select from two options: Triple DES and AES. By default, Password Manager uses Triple DES algorithm to encrypt data.

      NOTE: Users’ answers will be encrypted if the Store answers using reversible encryption option is selected in the Q&A Profile settings. Otherwise, the answers will be hashed.

    2. Encryption key length: Specify whether a 192-bit or 256-bit encryption key will be used.

    3. Hashing algorithm: Specify the hashing algorithm that will be used to hash users’ answers to secret questions. The following algorithms are available: MD5 and SHA-256. By default, Password Manager uses SHA-256 hashing algorithm. Password Manager will hash users’ answers if Store answers using reversible encryption option is not selected in the Q&A profile settings.

    4. Store user’s Questions and Answers profile in the following attribute of user’s account in Active Directory- In the text box, type the attribute name that will be used for storing Q&A profile data. By default, Password Manager stores Q&A profile data in the comment attribute of each user's account and configuration data in the comment attribute of a configuration storage account, which is automatically created when installing Password Manager.

  6. Click Save to complete instance initialization.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen