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

Password Manager 5.9.7 - Administration Guide (AD LDS Edition)

About Password Manager Getting Started Upgrading Password Manager Password Manager Architecture
Password Manager Components and Third-Party Solutions Typical Deployment Scenarios Password Manager in 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 Self-Service Site Configuring Access to the Helpdesk Site Configuring Questions and Answers Policy Workflow overview Custom workflows Custom Activities Self-Service 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 Unregistering users from Password Manager Working with Redistributable Secret Management account Email Templates
Password Policies One Identity Starling Reporting Appendix A: Accounts Used in Password Manager for AD LDS Appendix B: Open Communication Ports for Password Manager for AD LDS Appendix C: Customization Options Overview Glossary

One Identity Starling

Password Manager for AD LDS 5.9.7 supports integration with the One Identity Starling services. To connect to One Identity Starling, the Software as a Service (SaaS) solution of One Identity, use the Join to Starling feature of Password Manager for AD LDS.

To use One Identity Starling, you must have a One Identity Starling subscription. Each One Identity Starling subscription is registered with a phone number that receives token responses for authentication or push notifications. The type of token generation depends on the authentication method set for your subscription. Currently, Password Manager for AD LDS supports the following authentication methods:

  • SMS

  • Phone call

  • OTP on Starling 2FA app

  • Push notification

Prerequisites

To configure Starling for Password Manager for AD LDS, make sure that the following conditions are met:

  • Users have valid Starling credentials, that is a Starling Organization Admin account or a Collaborator account associated with their One Identity subscription. For more information, see the One Identity Starling User Guide.
  • Password Manager for AD LDS runs on the computer where you want to configure Starling.
  • Password Manager for AD LDS runs in a managed domain.

To configure One Identity Starling for authentication

NOTE: If you upgrade Password Manager for AD LDS, the Starling subscription key and the configuration details set for Starling Two-Factor Authentication will no longer be available. Therefore, you will need to perform the following steps again, and re-register with a valid Starling account.

  1. On the Password Manager Administration Site, navigate to One Identity Starling > One Identity Starling > Join to Starling.

  2. To start the configuration process, click Join to Starling. Password Manager for AD LDS then redirects you to the One Identity Starling website.

  3. To configure the Starling services available for your subscription, enter your One Identity Starling credentials.

    After a successful verification, you will be redirected to the One Identity Starling page.

    Once the information is saved, the Starling Join status appears.

  4. Perform the applicable step, depending on whether you already have a Starling account or not:

    • If you have a Starling account when the subscription is created for you, you will receive a Starling invitation email. Click the link in the email and log in to your Starling account.

    • If you do not have a Starling account when the subscription is created for you, you will receive a Starling sign-up email to complete the registration process to create your Starling account.

      Complete the registration and log in using the credentials that you provided during registration. For more information on creating a Starling account, see the One Identity Starling User Guide.

  5. For Starling Two-Factor Authentication, configure the user phone numbers in the appropriate Active Directory attribute.

    NOTE: Starling Two-Factor Authentication is available in the United States only.

  6. Under General Settings > Reinitialization, configure the same Active Directory attribute.

  7. Under Select the attribute of user’s account..., in the Method and Storage attribute table, configure Corporate phone. The default value is mobile.

To disconnect Password Manager for AD LDS from One Identity Starling

  1. On the Password Manager Administration Site, navigate to One Identity Starling > One Identity Starling > Unjoin Starling.

  2. To unjoin from the One Identity Starling service, click Unjoin Starling. This deletes the joined instances from One Identity Starling services and the Starling Join information from storage.

Once the disconnect process finished, the initial Join to Starling page appears.

One Identity Starling Two-Factor Authentication for Password Manager for AD LDS

Password Manager for AD LDS manages confidential user details both in on-premises and cloud-based environments. Therefore, One Identity strongly recommends using additional security measures, such as two-factor authentication to secure data. Available in the United States, Password Manager for AD LDS now supports the One Identity Starling Two-Factor Authentication service.

One Identity Starling Two-Factor Authentication (One Identity Starling 2FA) provides enhanced security by requiring users to provide two types of authentication to Password Manager for AD LDS: a user name and password combination, along with a token response. This token response is collected through an SMS, phone call, or push notification received on a physical device, for example a mobile.

Registering to One Identity Starling 2FA

To use Starling 2FA, you must register to the product. If you register with your mobile number, One Identity sends an SMS with a link of the Starling mobile app. Click the link to access the Apple App Store or Google Play Store from where you can download the Starling mobile app. Alternatively, visit the Apple App Store or Google Play Store, and download the Starling app manually.

Starling 2FA supports the following authentication options:

  • Push Notification: After the Starling app is downloaded and registered with the user email ID and mobile number, the user will receive push notifications to approve or deny Starling authentication.
  • Voice: The user will receive a voice call on the registered mobile number. During the call, the user will receive an OTP.
  • SMS OTP: The user will receive an OTP through SMS sent to their registered mobile number.
  • Users can also open the Starling app and copy the code from the Starling app to Password Manager for AD LDS. To authenticate with this code, click Verify.
Logging in to the Password Manager for AD LDS sites with Starling 2FA authentication

If a user has Starling 2FA enabled, attempting to log in to a Password Manager for AD LDS site results in Starling 2FA prompting the user to enter the configured token response. Based on the option selected by the user, the token response is provided through SMS, phone call or push notifications.

After entering the token response and verifying the user successfully, the Password Manager for AD LDS site appears.

 NOTE: Push notifications work only if the Starling app is installed on the device of the registered mobile number. The link to install the Starling app is sent to the registered mobile number at the time of registering to Starling.

Enable S2FA for Administrators and Enable S2FA for HelpDesk Users

This section describes the steps to enable Starling Two-Factor Authentication to protect AD LDS Administration site and Helpdesk site users.

To enable S2FA for Administrators and HelpDesk Users

  1. On the home page of the AD LDS Administration site, click the One Identity Starling tab.
  2. Select Enable S2FA for Administrators checkbox to protect the AD LDS Administration site or select Enable S2FA for HelpDesk Users checkbox to protect the HelpDesk site with Starling Two-Factor Authentication. Select both checkboxes to enable authentication for both Administration and HelpDesk user sites.

    		NOTE: The Administrator can choose if the user's mobile, or telephone number, or home phone number, or any other custom set attribute to be used for authentication from the Specify user's AD attribute for mobile number to authenticate the user dropdown box. The Administrator can also add a custom attribute to the existing list of attributes.
  1. Click Save to save the settings.

NOTE: The Administrator can choose which user’s active directory attributes to be used for the mobile number from the Specify user's AD attribute to authenticate the user dropdown box. The administrator can also specify other user’s active directory attribute for mobile number apart from the list.

 NOTE: If the administrator unjoins from the Starling, S2FA will stop the protection for AD LDS Administration and HelpDesk sites.
Failsafe Login

In case of One Identity Starling downtime situation, a failsafe method is provided by Password Manager to log in. For such case, Password Manager creates a user qpms2faadmin to log in. The qpms2faadmin user is managed by the administrator.

If the One Identity Starling is down while login to Password Manager, the AD LDS administration site prompts for user credential. The Administrator must provide the password for the qpms2faadmin user to authenticate and login to the AD LDS administration site.

Reporting

Reporting and User Action History Overview

Password Manager provides a simple and convenient way to view, print, and save reports and charts allowing you to analyze information on how the application is used. The reporting functionality within the solution is based on Microsoft SQL Server Reporting Services as a common reporting environment.

The Reports section of the Administrator site includes a number of pre-defined reports that help you perform the following tasks:

  • Track user registration activity
  • Analyze information about what actions are performed by users in Password Manager
  • Check users’ registration status
  • View a list of users whose Questions and Answers profiles must be updated to comply with the current administrator-defined settings
  • Track helpdesk operators’ activity

The user action history provides records of all actions performed by users registered with Password Manager. You can search for records using a full-text search functionality. The user action history is provided by Enterprise Auditing Service embedded in Password Manager.

To use Password Manager reports, you need to connect to an SQL Server and a Report Server.

To use the user action history functionality, you need to connect to an SQL Server only.

 

 

Alternative options

You can use predefined Power BI templates to generate interactive reports as an alternative to Reporting. For more information on Power BI, see Working with Power BI.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択