Chat now with support
Chat mit Support

Password Manager 5.13.1 - Administration Guide

About Password Manager Getting Started Password Manager Architecture
Password Manager Components and Third-Party Solutions Typical Deployment Scenarios Password Manager in Perimeter Network Management Policy Overview Password Policy Overview Secure Password Extension Overview reCAPTCHA Overview User Enrollment Process Overview Questions and Answers Policy Overview Password Change and Reset Process Overview Data Replication Phone-Based Authentication Service Overview
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 Notification Activities 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 Domain 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 Administrative Templates Secure Password Extension Password Policies Enable S2FA for Administrators & Enable S2FA for HelpDesk Users Reporting Password Manager Integration Accounts Used in Password Manager Open Communication Ports for Password Manager Customization Options Overview Feature imparities between the legacy and the new Self-Service Sites Glossary

Applying Password Policies

In Password Manager (PM) application, scopes can be defined at multiple levels. Scopes act as a boundary in which you can define the groups and Organization Unit (OU), and can also associate policies into it.

The Default Management Policy allows you to configure both the user scope and the helpdesk scope. In the Management Policy scope, administrators can also associate the workflows, activities, and Q&A policy to the configured user groups and OU.

While configuring the user scope/help desk scope, administrators must define either a Group or an OU to indicate which group or OU can access the Self-Service Site and/or Helpdesk Site. This means the users who are part of the configured group/OU comes under included group category. You could also define a different group/OU under an excluded group category. This means users who are part of this excluded group or OU cannot access the Self-Service Site andor Helpdesk Site.

In case of Password Policy scope, admin needs to ensure the following

  • Password policies must be applied only to the user groups and/or OUs that are part of the user scope.

  • The group that will be associated with the password policy scope must be part of the OU as well. This means that users who are part of the group must also be the part of the OU, as those users will have the same set of activities available to perform in the Self-Service Site.

  • Administrators can create one or more password policies and can map each policy to either a single or multiple user groups or OUs.

  • By default, the newly created password policy is linked to the Domain name created in the management policy scope and is applied to the Authenticated users group. This means that all users who are part of the user groups and OUs configured in the user scope will be affected by the password policy.

IMPORTANT:

  • While configuring the Policy Scope in the Password Policy Properties window, you must add both the group and the organizational unit that the user is a member of. This ensures that the policy rules will be applied to the user when accessing the Self-Service Site.

  • It is not possible to configure the same domain multiple times in a user scope, whereas multiple domains can be configured to the userscope.

The table below provides more information on different scenarios.

Let us consider the following groups/OU.

S.No Userscope

 

 

Password Policy Scope

 

 Password Policy Logged in self-service site

Is Password Policy applicable?

 

Included Group Included OU

Excluded Group

Excluded OU

OU Group
1. Group1 OU1

 

 

 OU1 Group1 Password Policy1 User1

Yes

2. Group1 OU2

Group2

 

 OU1 Group2

 

Password Policy2

 

 User2

No

3.

Group3

OU1

Group1

 

OU2

Group3

User2

No

4.

Group3

OU3

 

OU1

OU3

Group3

 

Password Policy3

 

User3

Yes

5.

Group2

OU2

 

 

OU1

Group2

User2

No

6.

Group1

OU1

 

OU4

OU4

Group1

 

Password Policy4

 

User1

No

7.

Group2

OU2

 

OU5

OU5

Group2

User2

No

8.

Group3

OU3

Group1

 

 

Group3

 

Password Policy 5

 

User3

No

9.

Group3

OU3

Group2

 

OU3

 

User3

No

To link a password policy to organizational units and groups

  1. Display properties of a password policy by using the procedure outlined in About Password Policies.

  2. Click the Policy Scope tab.

  3. Click the Add button under This policy is applied to the following organizational units, then browse for an organizational unit.

  4. Click the Add button under This policy is applied to the following groups, then browse for a group.

  5. Click Save.

Changing Policy Priority

When multiple password policies affect an organizational unit or a group, only the policy with the highest priority is applied to such group or organizational unit. A newly created password policy is disabled by default.

NOTE: Only priority of policies with the same scope can be changed.

To change policy priority

  1. On the home page of the Administration Site, click the Password Policies tab.

  2. Click the One Identity Password Policies link under the domain for which you want to change the policy link order and click Policy priority.

  3. In the Change Policy Priority dialog box, move policies up or down in the list by selecting them and clicking the Move Up or Move Down buttons.

Deleting a Password Policy

To delete a password policy from a domain

  1. On the home page of the Administration site, click the Password Policies tab.

  2. Click the One Identity Password Policies link under the domain that you want to manage.

  3. Click Remove under the policy that you want to delete.

NOTE: When you delete a password policy from a managed domain, the deleted policy is no longer valid for this domain.

To restore a deleted password policy, create a new policy and manually configure its settings as required.

Enable S2FA for Administrators & Enable S2FA for HelpDesk Users

This section describes the steps to enable 2FA to protect Administration site and Helpdesk site users.

To enable 2FA for Administrators & HelpDesk Users

  1. On the home page of the Administration site, click the Management/2FA enforcement tab.

  2. Select the Use Secure Token Server for authentication checkbox for admin authentication and/or helpdesk authentication, then choose one of the Secure Token Server providers, which you need to use for 2FA authentication. The login interface presentation can be selected from the Choose the behaviour of the authentication dropdown.

  3. Click Save to save the settings.

NOTE: At least one Secure Token Server provider needs to be configured. If there is an external provider, which loads their content while sending an X-Frame-Options : Deny header, the iframe option will not work. In this case, the redirect or the popup option is required.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen