Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Active Roles On Demand Hosted - 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

Default creation options for Exchange mailbox

In the wizard for creating user accounts, whether in the Active Roles console or Web Interface, the Create an Exchange mailbox option is selected by default, causing the user mailbox to be created upon creation of a user account. This behavior can be changed by applying an appropriately crafted policy of the Exchange Mailbox AutoProvisioning category.

A policy can be configured so that the Create an Exchange mailbox option is not selected by default but the administrator who uses the wizard to create a user account can select that option if necessary. It is also possible to configure a policy that forces the Create an Exchange mailbox option to be selected.

To set default creation options for Exchange mailbox

  1. Create a Policy Object containing an Exchange Mailbox AutoProvisioning policy.
  2. Open the Properties dialog box for the Policy Object you created.
  3. On the Policies tab in the Properties dialog box, double-click the Exchange Mailbox AutoProvisioning policy entry.
  4. On the Mailbox Creation tab in the Exchange Mailbox AutoProvisioning Policy Properties dialog box, set policy options as appropriate for your situation:
    • Create the user mailbox by default.  Determines whether the Create an Exchange mailbox option is selected by default in the wizard for creating user accounts. If you want user mailboxes not to be created by default, unselect this policy option.
    • Enforce creation of the mailbox.  Causes the Create an Exchange mailbox option to be selected and unavailable so that the administrator who creates a user account cannot unselect that option.
  5. Click OK to close the dialog boxes you opened.
  6. Apply the Policy Object to the scope (domains, containers, or Managed Units) where you want this policy to be in effect.

AutoProvisioning for SaaS products

Policies of this category are intended to automate the provisioning of users and groups in the selected SaaS products using Starling Connectors.

You can specify the Starling Connect connectors to be validated for the users or groups for which the policy is applied.

How this policy works

Active Roles relies on this policy during user creation to provision the users for connected systems based on the registered Starling Connectors that are selected based on the configured policy.

Create Provisioning policy for Starling Connect

To create a Policy Object for Starling Connect

  1. In the console tree, under Configuration | Policies | Administration, locate and select the folder in which you want to add the Policy Object.

    You can create a new folder as follows: Right-click Administration and select New | Container. Similarly, you can create a sub-folder in a folder: Right-click the folder and select New | Container.

  2. Right-click the folder, point to New, and then click Provisioning Policy.

  3. On the Welcome page of the wizard, click Next.

  4. On the Name and Description page, do the following, and then click Next:
    1. In the Name box, type a name for the Policy Object.

    2. Under Description, type any optional information about the Policy Object.
  5. On the Policy to Configure page, select Autoprovisioning in SaaS products, and click Next to configure policy settings.

  6. On the Object Type Selection page, click Select.

    1. On the Select Object Type, from the Object types list, select User or Group, and click OK.

    2. Click Next.

    3. On the Policy Conditions page, from the Starling Connect Connectors list, select the connectors to be provisioned for the user or group as part of the policy. Click Next.

  7. On the Enforce Policy page, you can specify the containers on which this Policy Object is to be applied:

    1. Click Add, and use the Select Objects to locate and select the objects you want.

    2. Click Next.

  8. Click Finish.

IMPORTANT: Starling Connect policy have to be applied on the container for any SaaS operations to take place.

SaaS operations for each connector may vary from each other. Each connector may have a set of mandatory attributes to perform any operation.

The operation will fail in case any of the mandatory attributes are missing in the particular request. The notification will report the information of all the mandatory attributes missing in that event which caused the failure.

In that case, you must create the corresponding virtual attributes, customize the Web Interface to enter the value for the virtual attribute during the specified operation. Using this approach, the attribute value is passed as a part of the request.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation