Chat now with support
Chat with Support

Active Roles 7.5.3 - Administration Guide

Introduction About Active Roles Getting Started Rule-based Administrative Views Role-based Administration
Access Templates as administrative roles Access Template management tasks Examples of use Deployment considerations Windows claims-based Access Rules
Rule-based AutoProvisioning and Deprovisioning
About Policy Objects Policy Object management tasks Policy configuration tasks
Property Generation and Validation User Logon Name Generation Group Membership AutoProvisioning E-mail Alias Generation Exchange Mailbox AutoProvisioning AutoProvisioning for SaaS products OneDrive Provisioning Home Folder AutoProvisioning Script Execution Office 365 and Azure Tenant Selection User Account Deprovisioning Office 365 Licenses Retention Group Membership Removal Exchange Mailbox Deprovisioning Home Folder Deprovisioning User Account Relocation User Account Permanent Deletion Group Object Deprovisioning Group Object Relocation Group Object Permanent Deletion Notification Distribution Report Distribution
Deployment considerations Checking for policy compliance Deprovisioning users or groups Restoring deprovisioned users or groups Container Deletion Prevention policy Picture management rules Policy extensions
Understanding workflow Workflow activities overview Configuring a workflow
Creating a workflow definition Configuring workflow start conditions Configuring workflow parameters Adding activities to a workflow Configuring an Approval activity Configuring a Notification activity Configuring a Script activity Configuring an If-Else activity Configuring a Stop/Break activity Configuring an Add Report Section activity Configuring a Search activity Configuring CRUD activities Configuring a Save Object Properties activity Configuring a Modify Requested Changes activity Enabling or disabling an activity Enabling or disabling a workflow Using the initialization script
Example: Approval workflow E-mail based approval Automation workflow Activity extensions
Temporal Group Memberships Group Family Dynamic Groups Active Roles Reporting Management History
Understanding Management History Management History configuration Viewing change history
Workflow activity report sections Policy report items Active Roles internal policy report items
Examining user activity
Entitlement Profile Recycle Bin AD LDS Data Management One Identity Starling Management One Identity Starling Two-factor Authentication for Active Roles Managing One Identity Starling Connect Azure AD, Office 365, and Exchange Online management
Configuring Active Roles to manage hybrid AD objects Managing Hybrid AD Users Unified provisioning policy for Azure O365 Tenant Selection, Office 365 License Selection, and Office 365 Roles Selection, and OneDrive provisioning Office 365 roles management for hybrid environment users Managing Office 365 Contacts Managing Hybrid AD Groups Managing Office 365 Groups Managing Azure Security Groups Managing cloud-only Azure users Managing cloud-only Azure guest users Managing cloud-only Azure contacts Changes to Active Roles policies for cloud-only Azure objects Managing room mailboxes
Managing Configuration of Active Roles
Connecting to the Administration Service Adding and removing managed domains Using unmanaged domains Evaluating product usage Creating and using virtual attributes Examining client sessions Monitoring performance Customizing the console Using Configuration Center Changing the Active Roles Admin account Enabling or disabling diagnostic logs Active Roles Log Viewer
SQL Server Replication Appendix A: Using regular expressions Appendix B: Administrative Template Appendix C: Communication ports Appendix D: Active Roles and supported Azure environments Appendix E: Enabling Federated Authentication Appendix F: Active Roles integration with other One Identity and Quest products Appendix G: Active Roles integration with Duo Appendix H: Active Roles integration with Okta

Adding or removing members from an AD LDS group

When adding members to an AD LDS group, you can add security principals that reside in AD LDS instances or in Active Directory domains. Examples of security principals are AD LDS users, and Active Directory domain users and groups.

  1. To add or remove members to or from an AD LDS group
  2. In the console tree, under AD LDS (ADAM), locate and select the container that holds the group.
  3. In the details pane, right-click the group, and click Properties.
  4. On the Members tab in the Properties dialog box, click Add.
  5. Use the Select Objects dialog box to locate and select the security principals that you want to add to the group. When finished, click OK.
  6. On the Members tab, select the group members that you want to remove from the group, and then click Remove.
  7. After making the changes that you want to the group, click OK to close the Properties dialog box.

When using the Select Objects dialog box to locate a security principal, you first need to specify the AD LDS directory partition or Active Directory domain in which the security principal resides: click Browse and select the appropriate partition or domain.

It is only possible to select security principals that reside in managed AD LDS instances or Active Directory domains; that is, you can select security principals from only the instances and domains that are registered with Active Roles.

Disabling or enabling an AD LDS user account

You can disable the account of an AD LDS user in order to prevent the user from logging on to the AD LDS instance with that account.

To disable or enable an AD LDS user account

  1. In the console tree, under AD LDS (ADAM), locate and select the container that holds the user account.
  2. In the details pane, right-click the user account, and do one of the following to change the status of the account:
    • If the user account is enabled, click Disable Account.
    • If the user account is disabled, click Enable Account.

If the AD LDS user whose account you want to disable is currently logged on to the AD LDS instance, that user must log off for the new setting to take effect.

Normally, an AD LDS user is enabled when the user is created. However, if the password of a new AD LDS user does not meet the requirements of the password policy that is in effect, the newly created user account will be disabled. Before you can enable the user account, you must set a password for it that meets the password policy restrictions. For instructions, see the sub-section that follows.

Setting or modifying the password of an AD LDS user

Each AD LDS security principal, such as an AD LDS user, must be assigned an account and password, which AD LDS uses for authentication. You can use the Active Roles console to set or modify the password of an AD LDS user.

To set or modify the password of an AD LDS user

  1. In the console tree, under AD LDS (ADAM), locate and select the container that holds the user account of the AD LDS user for whom you want to set or modify the password.
  2. In the details pane, right-click the user account, and then click Reset Password.
  3. In the Reset Password dialog box, type a password for the user in New password, and retype the password in Confirm password, or click the button next to New password to generate a password.
  4. Click OK to close the Reset Password dialog box.

The AD LDS user for whom you set or modify the password must use the new password the next time that the user logs on to AD LDS.

By default, an AD LDS instance running on Windows Server 2003 or later automatically enforces any local or domain password policies that exist. If you set a password for an AD LDS user that does not meet the requirements of the password policy that is in effect, Active Roles returns an error.

Adding an organizational unit to the directory

To keep your AD LDS users and groups organized, you may want to place users and groups in organizational units (OUs). In AD LDS, as well as in Active Directory or other Lightweight Directory Access Protocol (LDAP)-based directories, OUs are the most commonly used method for keeping users and groups organized. To create an organizational unit in AD LDS, you can use the Active Roles console as follows.

To add an organizational unit to the directory

  1. In the console tree under AD LDS (ADAM), right-click the container to which you want to add the OU, and select New | Organizational Unit.
  2. Type a name for the new OU, click Next, and then click Finish.

By default, OUs can only be added under OU (ou=), country/region (c=), organization (o=) or domain-DNS (dc=) object classes. For example, you can add an OU to o=Company,c=US but not to cn=Application,o=Company,c=US. However, the schema definition of the OU object class can be modified to allow other superiors.

You can create new AD LDS users and groups in an AD LDS organizational unit by using the New | User or New | Group command on that organizational unit, as discussed earlier in this section.

You can move an existing AD LDS user or group to an organizational unit by using the Move command on that user or group in the Active Roles console, or by using the drag-and-drop feature of the console.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating