ActiveRoles_SynchronizationServiceAdministrationGuide
ActiveRoles_SynchronizationServiceAdministrationGuide
Synchronization Service
Administration Guide
Copyright 2023 One Identity LLC.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this
guide is furnished under a software license or nondisclosure agreement. This software may be used
or copied only in accordance with the terms of the applicable agreement. No part of this guide may
be reproduced or transmitted in any form or by any means, electronic or mechanical, including
photocopying and recording for any purpose other than the purchaser’s personal use without the
written permission of One Identity LLC .
The information in this document is provided in connection with One Identity products. No license,
express or implied, by estoppel or otherwise, to any intellectual property right is granted by this
document or in connection with the sale of One Identity LLC products. EXCEPT AS SET FORTH IN THE
TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT,
ONE IDENTITY ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR
STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-
INFRINGEMENT. IN NO EVENT SHALL ONE IDENTITY BE LIABLE FOR ANY DIRECT, INDIRECT,
CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT
LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF
INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF
ONE IDENTITY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. One Identity makes
no representations or warranties with respect to the accuracy or completeness of the contents of this
document and reserves the right to make changes to specifications and product descriptions at any
time without notice. One Identity does not make any commitment to update the information
contained in this document.
If you have any questions regarding your potential use of this material, contact:
One Identity LLC.
Attn: LEGAL Dept
4 Polaris Way
Aliso Viejo, CA 92656
Refer to our Web site (http://www.OneIdentity.com) for regional and international office
information.
Patents
One Identity is proud of our advanced technology. Patents and pending patents may apply to this
product. For the most current information about applicable patents for this product, please visit our
website at http://www.OneIdentity.com/legal/patents.aspx.
Trademarks
One Identity and the One Identity logo are trademarks and registered trademarks of One Identity
LLC. in the U.S.A. and other countries. For a complete list of One Identity trademarks, please visit
our website at www.OneIdentity.com/legal/trademark-information.aspx. All other trademarks are
the property of their respective owners.
Legend
Deploying Synchronization Service for use with AWS Managed Microsoft AD23
Supported AWS Managed Microsoft AD deployment configuration 23
Synchronization Service features and limitations when used with AWS Managed
Microsoft AD 24
Getting started 31
Synchronization Service Console 31
Gear icon 32
Sync Workflows tab 33
Sync History tab 33
Connections tab 34
Mapping tab 34
Password Sync tab 35
Configuring diagnostic logging 36
How to synchronize identity data 37
Synchronization Service Management Shell 37
Cmdlet naming conventions 38
Getting help 38
About us 422
Contacting us 423
Within the same organization, identity information can be stored in many different data
systems, such as directories, databases, or formatted dump files. Managing identity
information and synchronizing it between these data systems can take a lot of time and
effort for administrators. In addition, performing data synchronization manually is error-
prone and can lead to duplicate information or incompatible data formats.
With Active Roles Synchronization Service, you can completely automate the process of
identity data synchronization between the data systems used in your enterprise
environment.
Synchronization Service increases data management efficiency by automating the
creation, deprovision and update operations between your data systems. For example, if an
employee joins or leaves the organization, Synchronization Service can automatically
update the related information in all data systems, reducing your administrative workload
and getting new users up and running faster.
The use of scripting capabilities provides a flexible way to:
l Automate day-to-day administration tasks.
l Integrate the administration of managed data systems with other business
processes.
To start synchronizing identity data, you must connect Synchronization Service to your
data systems with so-called "connectors". Connectors allow Synchronization Service to
access specific data systems, then read and synchronize data in that system according to
your settings.
Synchronization Service includes several built-in connectors that do not require any license
file. For the list of these connectors and more information on configuring them, see
External data systems supported with built-in connectors.
Scheduling capabilities
You can schedule running synchronization operations and automatically perform them on a
regular basis to satisfy your company’s policy and save time and effort.
Extensibility
To access external data systems, Synchronization Service employs special connectors. A
connector allows Synchronization Service to read and synchronize the identity data
contained in a particular data system. Out of the box, Synchronization Service includes
connectors that allow you to connect to the following data systems:
l Microsoft Active Directory Domain Services
l Microsoft Active Directory Lightweight Directory Services
l Microsoft Exchange Server
l Microsoft Skype for Business Server
l Microsoft Azure Active Directory
l Microsoft 365
Technical overview
The following illustration shows how Synchronization Service synchronizes data between
connected data systems.
Synchronization Service
Synchronization Service performs data synchronization operations and include the
Synchronization Service Console that provides a graphical user interface for managing
connections to data systems and data synchronization operations.
Capture Agent tracks changes to user passwords in the source Active Directory domain
and provides that information to Synchronization Service, which then synchronizes the
changes to the target connected data systems by using the password synchronization
rules you specified.
To synchronize passwords, install Capture Agent on each domain controller in the Active
Directory domain you want to use as a source for the password synchronization operations.
Sync workflows
A sync workflow is a set of synchronization steps (or synchronization operations) that
define how to synchronize objects between two connected data systems. A sync workflow
can comprise one or more synchronization steps. You can use the Synchronization
Service Console, a component of Synchronization Service, to configure as many sync
workflows as needed.
1. Make sure the system on which you want to install Synchronization Service meets the
system requirements described in the Active Roles Release Notes.
2. From the Active Roles installation package, run the Active Roles setup.
3. Follow the instructions in the setup wizard.
4. On the Ready to Install page, click Install. The wizard will then install the following
components:
l Synchronization Service Console: The graphical user interface of Active Roles
Synchronization Service.
l Management Shell: A command-line interface to synchronize data between
external data systems with Active Roles Synchronization Service. For more
information, see Synchronization Service Management Shell.
l All built-in connectors to connect Synchronization Service to external data
systems.
5. To exit the wizard, click Finish.
Prerequisites
l If you are using an Azure SQL Server, set the db_owner database role to the user of
the Azure SQL Server.
l If you are using an SQL Server, set the dbcreator server role to the user of
the SQL Server.
dbcreator is the minimum role that the user of the SQL Server or Azure SQL Server
requires for the initial configuration of Synchronization Service.
After you configure Synchronization Service, you can change its settings at any time using
the Configuration Wizard. To start the wizard, start the Synchronization Service Console
and click the gear icon in the upper right corner of the Synchronization Service Console.
Prerequisites
The hybrid environment must meet the following requirements to configure Azure
BackSync:
l Azure Active Directory (Azure AD) module version 2.0.0.131 or later must be
installed and configured.
l The Directory Writers role must be enabled in Azure AD. To enable the role, use the
following script:
$psCred=Get-Credential
Connect-AzureAD -Credential $psCred
$roleTemplate = Get-AzureADDirectoryRoleTemplate | ? { $_.DisplayName -eq
"Directory Writers" }
In addition, the user account you use to configure Azure BackSync must have the
following roles:
l User Administrator
l Exchange Administrator
l Application Administrator
You can perform Azure back-synchronization with Active Roles Synchronization Service,
either automatically or manually:
Prerequisites
The hybrid environment must meet the following requirements to configure Azure
BackSync manually:
l Azure Active Directory (Azure AD) module version 2.0.0.131 or later must be
installed and configured.
l You must authenticate the Azure tenant of the Azure AD for which you configure
back-synchronization. Also, you must consent Active Roles as an Azure application.
For more information, see Configuring Active Roles to manage Azure AD using the
GUI in the Active Roles Administration Guide.
l For the container where Active Roles performs back-synchronization, you must
enforce the built-in Azure AD policy that automatically sets the attribute
edsvaazureOffice365enabled to true.
l Your Active Roles user must have write permissions for the following attributes:
l edsvaAzureOffice365Enabled
l edsaAzureContactObjectId
l edsvaAzureObjectID
l edsvaAzureAssociatedTenantId
l Your Active Roles user must also have local administrator privileges on the machine
where Active Roles Synchronization Service is running.
NOTE: Consider the following when configuring manual Azure back synchron-
ization:
l You must perform the initial configuration and back synchronization of Azure
AD user IDs only once.
l Azure AD groups cannot be created in Federated or Synchronized
environments. Instead, Azure AD groups are created in Active Roles and are
synchronized to Azure AD using native Microsoft tools, such as Azure AD
Connect. To manage the Azure AD group through Active Roles, you must
perform periodic back synchronization to the on-premises AD.
You can configure automatic Azure BackSync via the (Settings) > Configure Azure
BackSync option of Active Roles Synchronization Service Console. After you finish
configuration, the Synchronization Service Console will automatically create the Azure
BackSync registration, its required connections, mappings and workflows.
For more information on setting up manual Azure BackSync, see Configuring automatic
Azure BackSync.
The Azure App is created automatically with the default name as ActiveRoles
AutocreatedAzureBackSyncApp_V2.
NOTE: After the Azure App is registered in Azure, you must not delete or modify the
application. The back synchronization operation will not work as expected in case you
modify or delete the registered Azure App.
Sync workflows
On the Synchronization Service Console, click Sync Workflows to view the sync workflow
named AutoCreated_AzureADBackSyncWorkflow_<tenant name> that is created as a result of
the Azure BackSync configuration. The workflow displays the following synchronization
update steps from Azure AD to Active Roles for users, groups, and contacts:
l Step 1: AutoCreated_UpdateFromAzureToARSForBackSyncWorkFlowUser_
<tenant> for users.
l Step 2: AutoCreated_
UpdateFromAzureToARSForBackSyncWorkFlowGroup_<tenant> for groups.
l Step 3: AutoCreated_
UpdateFromO365ToARSForBackSyncWorkFlowContact_<tenant> for
contacts.
Connections
On the Synchronization Service Console, click Connections to view the connections from
Active Roles, Azure AD, and Microsoft 365 to external data systems. The following
connections are configured and displayed by default:
l AutoCreated_ARSConnectorForBackSyncWorkFlow_<tenant>
l AutoCreated_AzureADConnectorForBackSyncWorkFlow_<tenant>
l AutoCreated_O365ConnectorForBackSyncWorkFlow_<tenant>
NOTE: Multiple tenants are supported in back synchronization. The connection name can
be identified using the name of the tenant.
Mapping
On the Synchronization Service Console, click Mapping to view the mapping rules which
identify the users, groups, or contacts in Azure AD and on-premises AD uniquely and map
the specified properties from Azure AD to Active Roles appropriately.
On the Mapping tab, click a connection name to view or modify the mapping settings for
the corresponding connection. The user, group, and contact mapping pair information is
displayed by default as a result of the Azure BackSync configuration. For example, the
property userprincipalname can be used to map users between on-premises AD and
Azure AD in a federated environment.
NOTE: Consider the following when working with mapping rules:
For more information, see Transferring sync workflows from Quick Connect in the Active
Roles Synchronization Service Administration Guide.
Communication ports
The following table lists the default communication ports used by Synchronization Service:
NOTE: This feature is officially supported starting from Active Roles 8.1.3 SP1 (build
8.1.3.10). It is not supported on Active Roles 8.1.3 (build 8.1.3.2) and earlier versions.
Active Roles Synchronization Service supports deployment and configuration in the
Amazon cloud to manage AWS Managed Microsoft AD object synchronization.
This allows you to:
l Synchronize directory data from an on-premises AD environment to AWS Managed
Microsoft AD.
l Synchronize passwords from an on-premises Active Directory to AWS Managed
Microsoft AD (with certain limitations).
NOTE: Support for AWS Managed Microsoft AD by Active Roles was tested only in this
configuration. Active Roles does not officially support managing AWS Managed Microsoft
AD environments in a hybrid deployment, that is, using an on-premises Active Roles
and/or SQL Server installation and hosting AD via AWS Directory Service.
However, when using Synchronization Service in an EC2 instance in the Amazon cloud, also
consider the following limitations.
For Active Roles installations deployed in Amazon Elastic Compute Cloud (EC2) instances
and SQL Servers hosted on Amazon Relational Database Service for SQL Server (RDS for
SQL Server) instances, the known EC2 and RDS limitations apply.
l For more information about the known EC2 limitations, see Launch template
restrictions, Hibernation limitations and (if applicable) Constraints on the size and
configuration of an EBS volume in the Amazon EC2 documentation.
l For more information about the known Amazon RDS limitations, see Quotas and
constraints in the Amazon RDS documentation.
Infrastructure requirements
To deploy and configure Active Roles for AWS Managed Microsoft AD, you must have access
to the following AWS services and resources:
l AWS Managed Microsoft AD deployed via AWS Directory Service.
l One or more Amazon Elastic Compute Cloud (EC2) instance(s) hosting the Active
Roles services and components.
The EC2 instance(s) must have, at minimum:
l 2 vCPUs running at 2.0 GHz.
l 4 GB of RAM.
NOTE: AWS Managed Microsoft AD support was tested with a single t2.large
EC2 instance.
l An Amazon Relational Database Service for SQL Server (RDS for SQL Server).
NOTE: AWS Managed Microsoft AD support was tested with an RDS instance
running the latest version of Microsoft SQL Server.
Make sure that all these components are discoverable or visible to each other.
TIP: For consistency, after you logged in to the EC2 instance, rename the virtual machine
to the same name that you originally defined for the EC2 instance in the AWS console.
TIP: If the domain join process ends with an error, check the specified DNS addresses
and Domain Admin credentials in the AWS console.
Prerequisites
Before starting the procedure, make sure that the EC2 and RDS instances are connected,
as described in Verifying connectivity between the EC2 and RDS instances.
To install and configure Synchronization Service for use with AWS Managed
Microsoft AD
Getting started
Gear icon
In the upper right corner of the Synchronization Service Console, you can click the
gear icon.
The Gear icon provides the following commands:
l Configure Sync Service: Starts a wizard that helps you change the configuration
settings of the current Synchronization Service instance.
l Import Configuration: Starts a wizard that helps you to import configuration
settings from a configuration file created by another instance of
Synchronization Service.
l Export Configuration: Starts a wizard that helps you to save the configuration
profile of the current Synchronization Service instance to a file. You can use this file
to apply the saved configuration to other instances of Active Roles Synchronization
Service deployed in your environment.
l Mail Profiles: Allows you to add, edit, or delete mail profiles for sending notification
emails about sync workflow runs. For more information on how to use the email
notification, see Using sync workflow alerts.
l Diagnostic Logging: Allows you to specify settings for writing Synchronization
Service diagnostic data to the Synchronization Service log file or Windows Event Log.
l Communication Port: Allows you to change the communication port number used
by the Synchronization Service.
l Configure Azure BackSync: Allows you to configure back synchronization
operation in Azure with on-premises Active Directory objects.
Connections tab
The Connections tab allows you to manage connections between the Synchronization
Service and the external data systems you want to use for data synchronization operations.
For more information on creating connections to external data systems supported out of
the box, see External data systems supported with built-in connectors.
On the Connections tab, you can use the following elements (some of these elements
become available only after you create at least one connection):
l Add connection: Allows you to create a new connection to an external data system.
l Filter by: Allows you to filter existing connections by the letters or text you type in
the text box. The filter applies to the connection names.
l Sort by: Allows you to sort existing connections by connection name, name of the
connector used, or the frequency of usage in sync workflow steps.
l <Connection Name>: Represents a connection to an external data system. You
can click a connection name to view or modify the corresponding connection settings.
l Connection settings: Allows you to view or modify settings for the connection.
l Synchronization scope: Allows you to view or modify synchronization scope for the
connection.
l Delete connection: Deletes the connection.
Mapping tab
The Mapping tab allows you to manage mapping pairs and mapping rules for existing
connections. To view or modify mapping pairs or rules for a connection, click the name of
that connection. For more information on mapping pairs and rules, see Mapping objects.
On the Mapping tab, you can use the following elements (some of these elements become
available only after you create at least one connection to an external data system):
l Filter by: Allows you to filter existing connections by the letters or text you type in
the text box. The filter only applies to the connection names.
When you click a connection name on this tab, you can manage mapping pairs for the
connection by using the following elements (some of these elements become available
after you create at least one mapping pair for the connection):
l Add mapping pair: Allows you to specify the types of objects in two connected
systems for which you want to create a mapping pair.
l <ObjectType1> - <ObjectType2>: Represents a mapping pair and displays the
object types that belong to the same mapping pair. You can click a mapping pair
to view and change the scope of conditions where the object types belonging to
that mapping pair will be mapped. To define these conditions, you can create
mapping rules.
l Schedule: Allows you to schedule a recurring map operation for the current
pair of objects.
l Map now: Allows you to manually run the map operation on the current pair
of objects.
l Delete: Deletes the mapping pair on which you click this link.
When you click a mapping pair, you can manage mapping rules for the mapping pair by
using the following elements (some of these elements become available only after you
create at least one mapping rule for the mapping pair):
l Map now: Allows you to manually run the map operation on the mapping pair by
using the conditions specified in the existing mapping rules.
l Unmap: Allows you to unmap the objects that were earlier mapped according to the
settings specified for the mapping pair.
l Schedule mapping: Allows you to schedule a recurring map operation for the
mapping pair.
l Add mapping rule: Allows you to create a rule that will define a condition for
mapping objects that belong to the mapping pair.
l Delete rule: Deletes the mapping rule on which you click this link.
l Move up: Moves the current mapping rule one position up in the list.
l Move down: Moves the current mapping rule one position down in the list.
1. In the upper right corner of the Synchronization Service Console, select Settings >
Diagnostic Logging.
2. In the dialog that opens, use the following options:
l Windows Event Log Level: Drag the slider to select one of the following
options to write Synchronization Service data to the Windows Event Log:
l Error, Warning, and Information: Records errors, warnings, and
information events generated by Synchronization Service to the
Windows Event Log.
l Error and Warning: Records error and warning events generated by
Synchronization Service to the Windows Event Log.
l Error: Records error events generated by Synchronization Service to the
Windows Event Log.
l Off: Disables writing Synchronization Service data to the Windows
Event Log.
l Synchronization Service log level: Drag the slider to select one of the
following logging levels for the Synchronization Service log:
l All Possible Events: Writes detailed diagnostic data to the
Synchronization Service log file.
l Important Events: Writes only essential events to the Synchronization
Service log file.
l Off: Disables writing data to the Synchronization Service log file.
3. When you are finished, click OK to apply your settings.
1. Connect the Synchronization Service to the data systems between which you want to
synchronize identity data.
For more information, see External data systems supported with built-in connectors.
2. Configure synchronization scope for the connected data systems.
For more information, see Modifying synchronization scope for a connection.
3. Create a sync workflow.
For more information, see Creating a sync workflow.
4. Create one or more steps in the sync workflow, and, if necessary, define
synchronization rules for these steps.
For more information, see Synchronizing identity data.
5. Run the sync workflow you have created.
For more information, see Running a sync workflow.
You can also use the Synchronization Service to automatically synchronize passwords from
a specified Active Directory domain to other connected data systems. For more
information, see Automated password synchronization.
NOTE: When loading Synchronization Service, your system may indicate that the certi-
ficate of some digitally-signed files published by One Identity are untrusted, and that you
must enable trust for the certificate issuer to run Synchronization Service. If this
happens, press either R (Run once) or A (Always run). One Identity recommends
selecting A to prevent this message appearing again.
Getting help
This section provides instructions on how to get help information for the cmdlets added by
Management Shell to the Windows PowerShell environment.
Feature Supported
The Active Directory Connector supports linked attributes existing in the Active Directory
schema. Linked attributes allow you to establish associations between two objects.
Linked attributes exist in pairs, as follows:
l Forward link attribute: This is a linked attribute that exists on a source object (for
example, the member attribute on the Group object). Forward link attributes can be
single-valued or multivalued.
l Back link attribute: This is a linked attribute that can be specified on a target
object (for example, the memberOf attribute on the User object). Back link attributes
are multivalued and they must have a corresponding forward link attribute. Back link
attributes are not stored in Active Directory. Rather, they are calculated based on the
corresponding forward link attribute each time a query is issued.
1. Install Capture Agent on all domain controllers in the source and target Active
Directory domains.
1. Install Capture Agent on all domain controllers in the source and target Active
Directory domains you want to participate in the SID history synchronization.
For more information on how to install Capture Agent, see Managing Capture Agent.
2. Use the Specified domain controller option to connect Synchronization Service to
the source and target domains.
Feature Supported
Feature Supported
Password synchronization No
Specifies whether you can synchronize user
passwords from an Active Directory (AD) domain to
the connected data system.
Prerequisites
Before creating a new Skype for Business Server connection, make sure that unsigned
Windows PowerShell scripts are allowed to run on the computer on which Active Roles
Synchronization Service is installed. This is required because Synchronization Service uses
Windows PowerShell scripts to work with Microsoft Skype for Business Server.
NOTE: To view the current Windows PowerShell initialization policy, use the Get-
ExecutionPolicy cmdlet supplied with Windows PowerShell. To change the Windows
PowerShell initialization policy, you can use the Set-ExecutionPolicy cmdlet of Windows
PowerShell.
provided for
this object
type.
provided for
this object
type.
For each of the previous Skype for Business Server object types, Synchronization Service
provides special attributes that allow you to read or write data in Skype for Business
Server. You can access and use these attributes from the Synchronization Service Console,
for example when selecting the source and target attributes you want to include in the
synchronization operation.
The following table shows the attributes provided by Synchronization Service and explains
what data you can read or write in Skype for Business Server by using a particular attribute
for every object, except the Skype for BusinessSettings object.
valued, string
Identity Single- Gets the unique identifier of the policy. Read
valued, string
Members Multivalued, Gets or sets the user accounts to which Read, write
reference the policy is applicable.
Name Single- Gets the name of the policy. Read
valued, string
ObjectClass Single- Gets the type of the Skype for Business Read
valued, string Server object.
The following table lists the Skype for BusinessSettings object attributes and the type of
data you can read or write in Skype for Business Server by using a particular attribute.
For more information about the attributes listed above, see Supported Skype for Business
Server data.
For more information about these and other attributes that Synchronization Service
provides for a Skype for Business Server user object, see Supported Skype for Business
Server data.
The following table lists the attribute value combinations that correspond to a particular
value in the Telephony option.
Feature Supported
Password synchronization No
Specifies whether you can synchronize user passwords from an Active
Directory (AD) domain to the connected data system.
1. Make sure that the Synchronization Service computer has the following
software installed:
l Oracle Client: Ensure Oracle Client is configured to connect to the Oracle
service that can be used to access Oracle Database that hosts the data you
want to work with.
l Oracle Net Services
l Oracle Data Provider for .NET
For supported versions of this software, see the System Requirements section
in the Active Roles Release Notes.
2. In the Synchronization Service Console, open the Connections tab.
3. Click Add connection, then use the following options:
l Connection name: Type a descriptive name for the connection.
l Use the specified connector: Select Oracle Database Connector.
4. Click Next.
5. On the Specify connection settings page, use the following options:
l Oracle service name: Specify the name of the Oracle service you want to use
to access Oracle Database. You can click Refresh to get a list of available
Oracle services.
l Access Oracle service with: Type the user name and password of the
account with which you want to access the Oracle service.
l To test the connection with the new parameters, click Test connection.
6. Click Next.
7. On the Specify how to select and modify data page, use the following options:
l Use data from this table: Allows you to select a database table that includes
the data you want to participate in the synchronization operations. You can
click Preview to preview the database table you have selected.
l Use an SQL query to specify data: Allows you to compose an SQL query
that provides a more flexible way for specifying the data for synchronization.
For example, you can use this option to specify multiple database tables.
8. Click Next.
9. On the Specify attributes to identify objects page, use the following options:
l Available attributes: Lists the attributes that are available in the external
data system. Use this list to select the attributes whose values you want to use
to generate a unique identifier for each object in the external data system. You
can filter attributes by typing in the text box at the top of this list. To select
multiple attributes, hold down CTRL and click to select attributes in the list.
l UniqueID attributes: Lists the attributes whose values are currently used to
generate a unique identifier for each object in the external data system.
1. Make sure that the Synchronization Service computer has the following
software installed:
l Oracle Client: Ensure Oracle Client is configured to connect to the Oracle
service that can be used to access Oracle Database that hosts the data you
want to work with.
l Oracle Net Services
l Oracle Data Provider for .NET
For supported versions of this software, see the System Requirements section
in the Active Roles Release Notes.
2. In the Synchronization Service Console, open the Connections tab.
3. Click Connection settings below the existing Oracle Database connection you
want to modify.
4. On the Connection Settings tab, click an appropriate item to expand it and use the
options it provides.
You can expand the following items:
l Specifying connection settings for Oracle Database
l Configuring advanced settings for an Oracle Database or Oracle Database user
account connection
l Specifying attributes to identify objects for Oracle Database
5. Click Save.
Below each of these options, you can use the following buttons:
l Add: Adds a new SQL query to the list.
l Edit: Allows you to edit the SQL query selected in the list.
l Delete: Deletes the SQL query selected in the list.
SQL queries run in the order they are listed. If necessary, you can rearrange the SQL
queries in the lists: select an SQL query in the appropriate list, then click the up or down
arrow button to move the query as necessary.
This SQL query illustrates how to add a new entry to the table named
SQLConnTest1 in Oracle Database to which you want to provision data from another
connected system.
In this sample query, Id stands for the attribute that uniquely identifies each object
in the Oracle Database.
This SQL query illustrates how to create a new user in the Oracle Database:
call dbms_utility.exec_ddl_statement('CREATE USER ' || :USERNAME || '
IDENTIFIED BY ' || :newPassword)
In this sample query:
l USERNAME refers to the name of the attribute that uniquely identifies the user in
the Oracle Database.
Feature Supported
Bidirectional Yes
synchronization
Specifies whether you can both
read and write data in the
connected data system.
After connecting Synchronization Service to the Oracle Database with the Oracle Database
User Accounts Connector, you can specify custom SQL queries that will automatically run
each time after Synchronization Service created, updated, or deleted a user account in
Oracle Database User Accounts. For more information, see Modifying an existing Oracle
Database connection.
Below each of these options, you can use the following buttons:
l Add: Adds a new SQL query to the list.
l Edit: Allows you to edit the SQL query selected in the list.
l Delete: Deletes the SQL query selected in the list.
SQL queries run in the order they are listed. If necessary, you can rearrange the SQL
queries in the lists: select an SQL query in the appropriate list, then click the up or down
arrow button to move the query as necessary.
This SQL query illustrates how to call a specific Oracle stored procedure:
CALL "<ProcedureName>"('&USERNAME')
In this query:
l ProcedureName specifies the name of the Oracle stored procedure you
want to call.
l USERNAME refers to the name of the attribute that uniquely identifies a user in
the target Oracle Database system.
This SQL query illustrates how to create a new user in the connected Oracle
Database:
insert into DatabaseTable(ColumnName) values (upper('&USERNAME'))
In this sample query:
l DatabaseTable specifies the name of the table into which the entry will
be added.
l USERNAME refers to the name of the attribute that uniquely identifies a user in
the target Oracle Database system.
Feature Supported
Password synchronization No
Specifies whether you can synchronize user passwords from an Active
Directory (AD) domain to the connected data system.
ActiveSyncMailboxPolicy Yes No No No
Allows you to read the Mobile Device mailbox
policy settings for a specified Mobile Device
mailbox policy.
This object type works with the Exchange
Server versions supported by Active Roles. For
more information on the Microsoft Exchange
Server versions supported by Active Roles,
see System requirements in the Active Roles
Release Notes.
AddressBookPolicy Yes No No No
Allows you to read data related to address
book policies.
This object type works with the Exchange
Server versions supported by Active Roles. For
more information on the Microsoft Exchange
Server versions supported by Active Roles,
see System requirements in the Active Roles
Release Notes.
AddressList Yes No No No
Allows you to read data related to a specified
address list.
This object type works with the Exchange
Server versions supported by Active Roles. For
more information on the Microsoft Exchange
Server versions supported by Active Roles,
see System requirements in the Active Roles
Release Notes.
DistributionGroup Yes Yes Yes Yes
Allows you to read or write data related to a
specified distribution group.
This object type works with the Exchange
Server versions supported by Active Roles. For
more information on the Microsoft Exchange
For each of the above-listed Exchange Server object types Synchronization Service
provides a number of special attributes that allow you to read and/or write the data related
to that object type in Exchange Server. You can access and use these attributes from the
Synchronization Service Console (for example, when selecting the source and target
attributes you want to participate in the synchronization operation).
The next sections describe the attributes provided by Synchronization Service and explain
what data you can read and/or write in Exchange Server by using a particular attribute.
Other attributes provided for the ActiveSyncMailboxPolicy object have the same names
and descriptions as parameters of the following Exchange Management Shell cmdlet:
l Get-ActiveSyncMailboxPolicy
Other attributes provided for the AddressBookPolicy object have the same names and
descriptions as parameters of the following Exchange Management Shell cmdlet:
l Get-AddressBookPolicy
Other attributes provided for the AddressList object have the same names and
descriptions as parameters of the following Exchange Management Shell cmdlet:
l Get-AddressList
Other attributes provided for the DistributionGroup object have the same names and
descriptions as parameters or return types of the following Exchange Management
Shell cmdlets:
l Enable-DistributionGroup
l Get-DistributionGroup
l Set-DistributionGroup
Other attributes provided for the DynamicDistributionGroup object have the same names
and descriptions as parameters or return types of the following Exchange Management
Shell cmdlets:
Other attributes provided for the ExchangeServer object have the same names and
descriptions as parameters of the following Exchange Management Shell cmdlet:
l Get-ExchangeServer
Other attributes provided for the GlobalAddressList object have the same names and
descriptions as parameters of the following Exchange Management Shell cmdlet:
l Get-GlobalAddressList
specified in the
LinkedDomainController
attribute.
LinkedCredentialPassword Single- Specifies the password that Write
valued, matches the user name
string specified in the
LinkedCredentialLogin
attribute.
MoveMailboxTo Single- Moves mailbox to the Exchange Write
valued, Server database whose name is
string specified in this attribute.
ObjectID Single- Gets the unique identifier for a Read
valued, specified object in Exchange
string Server.
RecipientTypeDetails Single- Gets or sets a mailbox type. Read, Write
valued,
When you create a mailbox
string
object, this attribute supports
the following values:
l DiscoveryMailbox
l EquipmentMailbox
l RoomMailbox
l SharedMailbox
l UserMailbox
Other attributes provided for the Mailbox object have the same names and descriptions as
parameters or return types of the following Exchange Management Shell cmdlets:
l Set-CalendarProcessing
l Get-CASMailbox
l Set-CASMailbox
l Disable-Mailbox (called by Archive and RemoteArchive attributes)
l Enable-Mailbox (called by Archive and RemoteArchive attributes)
l Get-Mailbox
l Set-Mailbox
l Get-MailboxAutoReplyConfiguration
l Set-MailboxAutoReplyConfiguration
l Get-MailboxStatistics
l Get-MoveRequest
l New-MoveRequest
l Remove-MoveRequest
l Set-MoveRequest
l Disable-UMMailbox (called by UMEnabled attribute)
l Enable-UMMailbox (called by UMEnabled attribute)
l Get-UMMailbox
l Set-UMMailbox
l Get-UMMailboxPIN
l Set-UMMailboxPIN
NOTE: Some attributes may perform actions by calling certain Exchange Management
Shell cmdlets, as noted in the table.
Other attributes provided for the MailContact object have the same names and
descriptions as parameters or return types of the following Exchange Management
Shell cmdlets:
l Enable-MailContact
l Get-MailContact
l Set-MailContact
NOTE: The Exchange Server Connector cannot create new users in Active Directory. You
can create new AD users with the Active Directory Connector.
Other attributes provided for the MailboxDatabase object have the same names and
descriptions as parameters of the following Exchange Management Shell cmdlet:
l Get-MailboxDatabase
NOTE: The Exchange Server Connector cannot create new users in Active Directory. You
can create new AD users with the Active Directory Connector.
Other attributes provided for the OfflineAddressBook object have the same names and
descriptions as parameters of the following Exchange Management Shell cmdlet:
l Get-OfflineAddressBook
Other attributes provided for the OrganizationConfig object have the same names and
descriptions as parameters of the following Exchange Management Shell cmdlet:
l Get-OrganizationConfig
Other attributes provided for the OwaMailboxPolicy object have the same names and
descriptions as parameters of the following Exchange Management Shell cmdlet:
l Get-OwaMailboxPolicy
Other attributes provided for the PublicFolder object have the same names and
descriptions as parameters of the following Exchange Management Shell cmdlet:
l Get-PublicFolder
Other attributes provided for the PublicFolderDatabase object have the same names and
descriptions as parameters of the following Exchange Management Shell cmdlet:
l Get-PublicFolderDatabase
Other attributes provided for the RoleAssignmentPolicy object have the same names and
descriptions as parameters of the following Exchange Management Shell cmdlet:
l Get-RoleAssignmentPolicy
Other attributes provided for the StorageGroup object have the same names and
descriptions as parameters of the following Exchange Management Shell cmdlet:
l Get-StorageGroup
Other attributes provided for the UmDialPlan object have the same names and descriptions
as parameters of the following Exchange Management Shell cmdlet:
l Get-UMDialPlan
Other attributes provided for the UmMailboxPolicy object have the same names and
descriptions as parameters of the following Exchange Management Shell cmdlet:
l Get-UMMailboxPolicy
Configure a connection to the Exchange Server installation you will use to move the
mailbox object. For more information on the Microsoft Exchange Server versions supported
by Active Roles, see System requirements in the Active Roles Release Notes.
NOTE: Both the source and target computers must have either the same Exchange
Server Service Packs installed, or no Exchange Server Service Packs installed at all.
For more information on how to configure a connection to Exchange Server, see Creating a
new connection to Exchange Server.
For more information on how to create a new sync workflow, see Creating a sync workflow.
For instructions on how to create and configure an update step, see Creating an
update step.
For more information on how to run a sync workflow, see Running a sync workflow.
Feature Supported
The Active Roles Connector supports linked attributes in the Active Directory schema.
Linked attributes allow you to associate one object with another object. Linked attributes
exist in pairs:
Feature Supported
Password synchronization No
Specifies whether you can synchronize user passwords from an Active
Directory (AD) domain to the connected data system.
For example:
<ExcludeDeletedObjects>
TRUE
</ExcludeDeletedObjects>
<PasswordAttributes>
<PasswordAttributeDefinitions>
<PasswordAttributeDefinition objectType-
For more information about the FullSync variable and the values it can take, see the One
Identity Manager documentation.
Feature Supported
Bidirectional synchronization No
Specifies whether you can both read and write data in the connected data
system.
Password synchronization No
Specifies whether you can synchronize user passwords from an Active
Directory (AD) domain to the connected data system.
Schema
You can use this expandable item to view and modify the delimited text file schema saved
in the Synchronization Service configuration database.
When you create a connection to a delimited text file, Synchronization Service reads the
schema in the file (that is, the fields or columns related to each record in the file), and then
saves the schema in the Synchronization Service configuration database. Synchronization
Service then uses the saved file schema to read and modify the data in the connected file.
Should the schema in the connected file change, you will need to reflect these changes in
the Schema option so that Synchronization Service could correctly handle (read and write)
the data in the changed file.
This expandable item provides the following options:
l Attributes: Lists the names of Synchronization Service attributes that correspond to
certain columns or fields in the connected file. Basically, these are the names of
attributes you can select and use in the Synchronization Service Console for each
object in the connected delimited text file.
l Add: Allows you to add a new entry (for example, column or field) to the file
schema saved in the Synchronization Service configuration database. You can use
this button in case a new column or field was added to the connected file and you
want to reflect this change in the file schema saved in the Synchronization Service
configuration database.
l Edit: Allows you to edit the name of the selected Synchronization Service attribute
associated with a certain column or field in the connected file. For example, you can
Feature Supported
Advanced
Allows you to configure the running timeout for all SQL queries you specified in the
connection settings (for example, those specified in the Specify How to Select and
Modify Data option). Use the SQL query execution timeout box to type the timeout
value you want to use.
This sample illustrates how to create a query that inserts an object with specified
attributes into the table named SQLConnTest1.
This sample illustrates how to create a SQL Server account, and then retrieve the
UniqueID attribute for that account.
To define the scope where to create the SQL Server account, insert the following
query in the Query Editor dialog:
SELECT sid as Id,name as login from sys.server_principals
Insert the following SQL query into the Configure SQL Statements dialog:
EXEC sp_addlogin @login, @newPassword;
EXEC sp_adduser @login,@login,'db_owner';
SELECT sid as Id from sys.server_principals where name=@login;
IMPORTANT: None of the attribute names used in SQL queries can include
whitespace characters. For example, you cannot use names such as "user
password".
Feature Supported
Feature Supported
For instructions on how to create a new connection to an Active Directory domain, see
Creating an Active Directory connection.
For instructions on how to create a new connection to Salesforce, see Creating a Salesforce
connection.
For instructions on how to create a new sync workflow for the configured Salesforce
connection, see Scenario: Provisioning users from an Active Directory domain to
Salesforce.
Once the required connections and the sync workflow are set, configure a new
workflow step.
1. In the Synchronization Service Console, navigate to the Workflows tab and open
the sync workflow you created by clicking its name. Then, click Add
synchronization step.
2. On the Select an action page, click Provision, then click Next.
3. On the Specify source and criteria page, do the following:
a. Click Specify in the Source connected system option, then click Select
existing connected system, and select the Active Directory connection you
configured in the Configuring a connection to source Active Directory
domain step.
b. Click Finish.
c. In Source object type, click Select, then select the User object type from
the list. Click OK.
d. Click Next.
4. On the Specify target page, do the following:
a. Click Specify in the Target connected system option, then click Select
existing connected system, and select the Salesforce connection you
configured in the Configuring a connection to Salesforce step.
b. Click Finish.
c. Click Select in the Target object type option, then select the User object
type from the list. Click OK.
d. Click Next.
5. On the Specify provisioning rules page, in the Initial Attribute Population
Rules option, add rules to populate the following required attributes:
l Username: Use this attribute to specify a Salesforce user name for the user
being provisioned. Make sure the user name you specify meets the format
For instructions on how to run a sync workflow, see Running a sync workflow.
Feature Supported
Specifies whether the connector can use SSL to encrypt data transmitted
between Active Roles Synchronization Service and the connected data
system.
Configuring ServiceNow
To configure ServiceNow
Feature Supported
Specifies whether you can both read and write data in the connected data
system.
Feature Supported
To specify the target object type and attribute for storing passwords
1. Click the Connection settings link below the LDAP directory service connection for
which you want to specify the target object type and attribute for storing passwords.
2. Open the Password tab.
Feature Supported
After establishing a connection, you can define attributes to name objects in the data
system. For more information, see Modifying an existing Generic LDAP directory
service connection
Feature Supported
1. On the system where Synchronization Service is installed, install IBM Data Server
Client supplied with the IBM DB2 version with which you plan to work.
2. In the Synchronization Service Console, open the Connections tab.
3. Click Add connection, then use the following options:
l Connection name: Type a descriptive name for the connection.
l Use the specified connector: Select IBM DB2 Connector.
4. Click Next.
5. On the Specify connection settings page, use the following options:
l IBM DB2 server: Type or select the fully qualified domain name of the IBM
DB2 computer that hosts the database you want to participate in data
synchronization operations. You can click Refresh to get a list of available IBM
DB2 servers.
l Access IBM DB2 server using: Type the user name and password with
which you want to access the IBM DB2 server.
l Connect to database: Type the name of the database to which you want to
connect on the IBM DB2 server.
l Advanced: Optionally, you can click this button to specify additional
parameters you want to add to the connection string that will be used to
access the IBM DB2 server. In the dialog box that opens, click Add
Parameter to specify the name and value of the parameter you want to add
to the connection string.
l To test the connection with the new parameters, click Test connection.
6. Click Next.
7. On the Specify how to select and modify data page, use the following options:
l Use data from this table: Allows you to select a database table that includes
the data you want to participate in the synchronization operations. You can
click Preview to preview the database table you have selected.
l Use an SQL query to specify data: Allows you to compose an SQL query
Advanced
Allows you to configure the running timeout for all SQL queries you specified in the
connection settings (for example, those specified in the Specify How to Select and
Modify Data option). Use the SQL query execution timeout box to type the timeout
value you want to use.
Feature Supported
Prerequisites
l The IBM AS/400 server must have LDAP directory services installed and configured.
l An LDAP service account must be created on your IBM AS/400 server which has the
appropriate permissions to administer users and groups on this platform.
The IBM AS/400 operating system does not have any concept of groups as discrete entities.
Instead, an administrator creates a user profile which is used as a group profile. Other user
profiles are then linked to this using the GrpPrf or SupGrpPrf parameters of the ChgUsrPrf
command. The GrpPrf value maps to the os400-grpprf attribute in the IBM AS/400 schema,
while the SupGrpPrf value maps to the os400-supgrpprf attribute. The IBM AS/400 Quick
Connect mappings must be defined for users and groups to enable full user and group
synchronization.
You can optionally unlock a user's IBM AS/400 account at the same time as performing a
password reset. This functionality is switched off by default and can be enabled by editing
the connector's configuration file as follows:
<SelfConfig>
<EnableAccount>true</EnableAccount>
</SelfConfig>
NOTE: Only the value true will enable the new functionality.
The LDAP password request sent to IBM AS/400 will then also include a request to modify
the account status (os400-status=*ENABLED)).
The configuration file is read every time an LDAP connection is made to the IBM AS/400, so
the new value will be picked up for the next set of synchronizations.
NOTE: If you edited ConnectorConfig.xml to implement the optional unlock of a user's
IBM AS/400 account at the same time as performing a password reset in an earlier
version of the connector for IBM AS/400, then you will need to repeat that edit after
installing a later version.
Feature Supported
NOTE: There is an 8 character limit for user and group names on IBM RACF. The
character limit is also applicable to the passwords on IBM RACF.
Audit nchar(100)
Create_Group nchar(10)
Owner nchar(10)
UACC nchar(10)
Create a connection to this database and table with the ARSS Microsoft SQL Server
Connector.
UACC racfUacc
Create_Group racfCreateGroup
Audit racfAudit
UID racfDataset
1. Navigate to the Sync Workflows tab, select IBM RACF Datasets and click OK.
2. Click Add synchronization step.
3. Click Update and then click Next.
4. From the Source connected system section and click Specify.
5. Select your Microsoft SQL Server Connector and click Finish.
The SQL source object type is currently set to sql-Object. Do not change this value.
6. Click Next.
7. In the Target connected system field, click Specify and then locate your IBM
RACF connector and click Finish.
8. The object type in the Target object system field is populated automatically by
Synchronization Service to racfUser. Change this to racfDataset.
9. Click Next.
10. In the Specify provisioning rules section, click Forward Sync Rule.
11. In the Source attribute field, click Attribute locate UID and click OK.
12. In the Target attribute field, click Attribute, locate racfDataset and click OK.
13. Repeat these steps so that the following five items are mapped:
UACC racfUacc
Create_Group racfCreateGroup
Audit racfAudit
UID racfDataset
Feature Supported
Prerequisites
Before configuring the connector, make sure that the Connector/NET fully-managed
ADO.NET driver is installed on the machine running the Synchronization Service.
Advanced
Allows you to configure the running timeout for all SQL queries you specified in the
connection settings (for example, those specified in the Specify How to Select and
Modify Data option). Use the SQL query execution timeout box to type the timeout
value you want to use.
Feature Supported
Bidirectional synchronization No
Specifies whether you can both read and write data in the NOTE: By using OLE DB
connected data system. Connector, you can only
read data in the
connected data system.
Password synchronization No
Specifies whether you can synchronize user passwords from
an Active Directory (AD) domain to the connected data
system.
Advanced
Allows you to configure the running timeout for all SQL queries you specified in the
connection settings (for example, those specified in the Specify How to Select and
Modify Data option). Use the SQL query execution timeout box to type the timeout
value you want to use.
Feature Supported
Password synchronization No
Specifies whether you can synchronize user passwords from an Active
Directory (AD) domain to the connected data system.
1. Ensure that you have installed the SharePoint Connector on the SharePoint server
you want to work with.
2. In the Synchronization Service Console, open the Connections tab.
3. Click Add connection, then use the following options:
l Connection name: Type a descriptive name for the connection.
l Use the specified connector. Select SharePoint Connector.
4. Click Next.
5. To check that the connector can access SharePoint, on the Specify connection
settings page, click the Test Connection.
6. If the test succeeds, click Finish to create a connection.
AlternateURL Yes No No No
Allows you to read data related to an incoming
URL and the zone with which it is associated.
ClaimProvider Yes No No No
Allows you to read data related to a claim
provider.
Farm Yes No No No
Allows you to work with a SharePoint farm.
Language Yes No No No
Allows you to work with a language used in
SharePoint.
Prefix Yes No No No
Allows you to work with a relative URL that
determines segments of the URL under which
sites may be created.
WebTemplate Yes No No No
Allows you to work with a site definition
configuration or a web template used to create
SharePoint sites.
The following sections describe the attributes provided by Synchronization Service and
describe what data you can read or write in SharePoint by using a particular attribute.
string
IsEnabled Single-valued, Gets whether the claims provider Read
Boolean is enabled.
IsUsedByDefault Single-valued, Gets whether the claims provider Read
Boolean applies by default to all web
applications and zones.
IsValid Single-valued, Gets whether the claims provider Read
Boolean is valid.
IsVisible Single-valued, Gets whether the claims provider Read
Boolean is visible.
Parent Single-valued, Gets the parent of the object. Read
string, reference
(Farm object)
TypeName Single-valued, Gets the type of the object. Read
string
messages.
PasswordChangeGuardTime Single- Gets the time Read
valued, interval (in
integer seconds) that
is used to wait
for other
computers’
response
during
password
change
operations.
PasswordChangeMaximumTries Single- Gets the Read
valued, maximum
integer allowed
number of
password
change
attempts
before the
operation fails.
PersistedFileChunkSize Single- Gets the chunk Read
valued, size used to
integer transfer files to
or from the
configuration
database
during a read
or write
operation.
Products Multivalued, Gets the Read
string identifiers of
products
installed in the
farm.
ServerDebugFlags Multivalued, Gets server Read
integer debug flags.
Servers Multivalued, Gets the Read
string physical
servers that
are included in
the farm.
TimerService Single- Gets the timer Read
valued, service that is
string used by the
farm.
TraceSessionGuid Single- Gets the GUID Read
valued, that is used for
string trace session
registration.
UseMinWidthForHtmlPicker Single- Gets the HTML Read
valued, select control.
Boolean
UserLicensingEnabled Single- Gets whether Read
valued, user licensing
Boolean is enabled.
XsltTransformTimeOut Single- Gets the Read
valued, timeout period
integer (in seconds) for
a customized
XSLT
transformation
operation.
string
LoginName Single-valued, Gets the login name Read
string of the group.
Name Single-valued, Gets or sets the Read, write
string name of the group.
OnlyAllowMembersViewMembership Single-valued, Gets or sets Read, write
Boolean whether only group (update only)
members can view
the list of members
for the group.
Owner Single-valued, Gets or sets the Read, write
string, group owner. A (create only)
reference group owner can be
(User or Group a user or another
object) group.
Parent Single-valued, Gets the parent of Read
string, the object.
reference
(Site object)
RequestToJoinLeaveEmailSetting Single-valued, Gets or sets the Read, write
string email address that (update only)
receives requests to
join or leave the
group.
Users Multivalued, Gets or sets the Read, write
string, users that are (update only)
reference members of the
(User object) group.
Xml Single-valued, Gets the group Read
string properties in the
XML string format.
DenyRightsMask Multivalued, string Gets or sets the rights which Read, write
the policy role denies. (update only)
Description Single-valued, string Gets or sets the policy role Read, write
description. (update only)
GrantRightsMask Multivalued, string Gets or sets the rights which Read, write
the policy role grants. (update only)
Id Single-valued, string Gets the policy role GUID. Read
IsSiteAdmin Single-valued, Gets or sets whether the Read, write
Boolean policy role grants site (update only)
collection administrator
status.
IsSiteAuditor Single-valued, Gets or sets whether the Read, write
Boolean policy role grants site (update only)
collection auditor status.
Name Single-valued, string Gets or sets the policy role Read, write
name. (update only)
Parent Single-valued, string, Gets the parent of the object. Read
reference
(WebApplication
object)
Type Single-valued, string Gets the type of the policy Read
role.
Xml Single-valued, string Gets the policy role in the Read
XML string format.
(RoleDefinition assignment.
object)
BasePermissions Multivalued, Gets or sets the base permissions for Read, write
string a role definition. (update only)
Description Single-valued, Gets or sets the role definition Read, write
string description. (update only)
Hidden Single-valued, Gets whether the role definition is Read
Boolean displayed in the user interface.
Id Single-valued, Gets the object identifier. Read
string
Members Multivalued, Gets or sets role assignments for the Read, write
string, role definition. (update only)
reference
Name Single-valued, Gets or sets the role definition name. Read, write
string
Order Single-valued, Gets or sets the order in which to Read, write
string display the permission levels in the (update only)
user interface.
Parent Single-valued, Gets the object parent. Read
string,
reference
Type Single-valued, Gets the role definition type. Read
string
Xml Single-valued, Gets the role definition permission in Read
string the XML format.
checks.
ContentDatabase Single- Gets the content database Read
valued, associated with the site
string collection.
CurrentChangeToken Single- Gets the change token that is Read
valued, used to write the next change
string to the site collection.
CurrentResourceUsage Single- Gets the resource usage for Read
valued, the site collection.
string
DeadWebNotificationCount Single- Gets the number of Read
valued, notifications that were sent
integer about the websites that are
not in use within the site
collection.
DenyPermissionsMask Multivalue Gets or sets the deny Read,
d, string permission mask for all site write
users, including the site (update
administrator. only)
EvalSiteId Single- Gets the identifier of the Read
valued, upgrade evaluation site
string collection, if it was created for
(GUID) the site collection.
ExpirationDate Single- Gets or sets the date after Read,
valued, which an upgrade evaluation write
DateTime site collection gets (update
automatically deleted. only)
FileNotFoundUrl Single- Gets the URL to the file not Read,
valued, found page. write
string (update
The HTTP requests where the
only)
resource cannot be found are
redirected to this URL.
HasAppPrincipalContext Single- Gets whether the object is Read
valued, running within an application
Boolean principal context.
HideSystemStatusBar Single- Gets whether the system Read
reset operation.
ResourceQuotaExceededNotificati Single- Gets whether a resource Read
onSent valued, quota exceeded notification
Boolean was sent since the last daily
quota reset operation for the
site collection.
ResourceQuotaWarningNotificatio Single- Gets whether a resource Read
nSent valued, quota exceeded warning was
Boolean sent since the last daily quota
reset operation for the site
collection.
SchemaVersion Single- Gets the site collection Read
valued, version number for upgrade
string compatibility checks.
SecondaryContact Single- Description is not available. Read,
valued, write
string, (update
reference only)
(User
object)
ServerRelativeUrl Single- Gets or sets the server- Read,
valued, relative URL of the root write
string website. (update
only)
ShareByEmailEnabled Single- Gets or sets whether the Read,
valued, users are allowed to grant write
Boolean access permissions to guests, (update
so that they could access the only)
site collection resources.
ShareByLinkEnabled Single- Gets or sets whether the Read,
valued, users are allowed to share write
Boolean the site collection documents (update
by providing hyperlinks to only)
those documents.
ShowURLStructure Single- Gets or sets whether to show Read,
valued, the site collection URL write
Boolean structure. (update
only)
number.
NOTE: This attribute is
required to create a new
site collection in
SharePoint.
UserCodeEnabled Single- Gets whether the user code Read
valued, service is enabled for the site
Boolean collection.
UserCodeMaximumLevel Single- Gets or sets the maximum Read,
valued, allowed resource usage for write
string the site. (update
only)
UserCodeWarningLevel Single- Gets or sets the warning limit Read,
valued, of the resource usage. When write
string this limit is exceeded, a (update
warning email will be sent to only)
site administrators.
UserDefinedWorkflowsEnabled Single- Gets or sets whether user- Read,
valued, defined workflows are write
Boolean enabled for the site (update
collection. only)
UserIsSiteAdminInSystem Single- Gets whether the current Read
valued, user is a site collection
Boolean administrator.
UserToken Single- Gets the user token Read
valued, associated with the site
binary collection
WarningNotificationSent Single- Gets whether a warning Read
valued, notification has been sent.
Boolean
WebTemplate Single- Description is not available. Read,
valued, write
string
WriteLocked Single- Gets whether the site Read
valued, collection is unavailable for
Boolean Write access.
(Group
object)
AssociatedVisitorGroup Single- Gets or sets the Read,
valued, associated visitor write
string, group of the
reference website.
(Group
object)
Author Single- Gets or sets the Read,
valued, user who created write
string, the website.
reference
(User
object)
CacheAllSchema Single- Gets or sets Read,
valued, whether caching of write
Boolean all schemas of the (update
website is enabled. only)
ClientTag Single- Gets or sets the Read,
valued, client cache control write
string number for the (create
(integer) website. only)
Configuration Single- Gets the ID of the Read
valued, site definition
string configuration that
(integer) was used to create
the website or the
template from
which the website
was created.
Created Single- Gets or sets the Read,
valued, date and time when write
string the website was (update
(DateTime) created. only)
CurrencyLocaleID Single- Gets or sets the Read,
valued, identifier of the write
string currency that is (update
(integer) used on the only)
website.
exposed through
the Site Data Web
Service.
IsADAccountCreationMode Single- Gets whether user Read
valued, accounts are
Boolean created
automatically in
Active Directory
when users are
invited to the
website.
IsADEmailEnabled Single- Gets whether email Read
valued, for AD DS is
Boolean enabled on the
website.
IsAppWeb Single- Gets whether the Read
valued, website is a
Boolean container for an
application.
IsMultilingual Single- Gets or sets Read,
valued, whether the write
Boolean website has a (update
multilingual user only)
interface enabled.
IsRootWeb Single- Gets whether the Read
valued, website is the top-
Boolean level site in the site
collection.
Language Single- Gets or sets the Read,
valued, locale identifier of write
reference the default (create
(Language language for the only)
object) website.
LastItemModifiedDate Single- Gets or sets the Read,
valued, date and time when write
string the last (update
(DateTime) modification was only)
made to an item on
the website.
object)
ParserEnabled Single- Gets or sets Read,
valued, whether parsing is write
Boolean enabled for (update
document libraries only)
of the website.
PortalMember Single- Gets whether the Read
valued, website is
Boolean associated with a
portal site.
PortalName Single- Gets the name of Read
valued, the portal site
string associated with the
website.
PortalSubscriptionUrl Single- Gets the URL that is Read
valued, used for alerts
string within the portal.
PortalUrl Single- Gets the URL that Read
valued, points to the portal
string site associated with
the website.
PresenceEnabled Single- Gets or sets Read,
valued, whether inline write
Boolean presence (update
information is only)
enabled for the
website.
Provisioned Single- Gets or sets Read,
valued, whether the write
Boolean website has been (update
provisioned. only)
QuickLaunchEnabled Single- Gets or sets Read,
valued, whether the Quick write
Boolean Launch area is (update
enabled and only)
available on the
website.
o)
UIVersion Single- Gets or sets the Read,
valued, current version write
string number of the user (update
(integer) interface. only)
Url Single- Gets or sets the Read,
valued, absolute URL of the write
string website. (create
only)
UserIsSiteAdmin Single- Gets whether the Read
valued, user has
Boolean administrator rights
on the website.
UserIsWebAdmin Single- Gets whether the Read
valued, user is a member of
Boolean the Administrator
group for the
website.
WebTemplate Single- Gets the name of Read
valued, the site definition or
string template that was
used to create the
website.
WebTemplateId Single- Gets or sets the ID Read,
valued, of the template or write
string definition that was (create
(integer) used to create the only)
website.
scriptable Web
Parts.
AllowDesigner Single- Gets or sets Read,
valued, whether websites write
Boolean within the web (update
application can be only)
edited with
SharePoint
Designer.
AllowedInlineDownloadedMimeTypes Multivalue Gets the MIME Read
d, string content types that
are not force-
downloaded to the
computer of the
user.
Files not listed in
this attribute value
are considered to be
script files and can
interact with the
web application on
the user’s behalf.
AllowHighCharacterListFolderNames Single- Gets or sets Read,
valued, whether non- write
Boolean alphanumeric (update
characters are only)
allowed in the list
folder names that
are generated
automatically.
AllowMasterPageEditing Single- Gets or sets Read,
valued, whether the users write
Boolean are allowed to edit (update
master pages. only)
AllowOMCodeOverrideThrottleSettings Single- Gets or sets Read,
valued, whether custom write
Boolean object model code is (update
allowed to override only)
the throttle
settings.
AllowPartToPartCommunication Single- Gets or sets Read,
valued, whether the Web write
Boolean application allows (update
communication only)
between different
Web Parts.
AllowRevertFromTemplate Single- Gets or sets Read,
valued, whether customized write
Boolean sites can be rolled (update
back to their base only)
templates.
AllowSelfServiceUpgradeEvaluation Single- Gets or sets Read,
valued, whether upgrade write
Boolean evaluation site (update
collections can be only)
created.
AllowSilverlightPrompt Single- Gets or sets Read,
valued, whether UI write
Boolean elements that (update
require Microsoft only)
Silverlight prompt
the user to
download and install
Silverlight.
AlwaysProcessDocuments Single- Gets or sets Read,
valued, whether documents write
Boolean to be returned are (update
always processed only)
by document
parsers.
ApplicationPrincipalMaxRights Multivalue Gets or sets the Read,
d, string maximum rights write
that any application (update
principal user has in only)
the web application.
AutomaticallyDeleteUnusedSiteCollection Single- Gets or sets Read,
s valued, whether to write
Boolean (update
web application
pages.
MaximumFileSize Single- Gets or sets the Read,
valued, maximum file size write
integer limit for files to be (update
uploaded. only)
MaxItemsPerThrottledOperation Single- Gets or sets the Read,
valued, count of items at write
integer which throttling (update
begins for list only)
operations.
MaxItemsPerThrottledOperationOverride Single- Gets or sets the Read,
valued, maximum count of write
integer items for which (update
throttling is not only)
enabled if the
current user is an
administrator or
auditor.
MaxItemsPerThrottledOperationWarningLev Single- Gets or sets the Read,
el valued, warning level for the write
integer number of items in (update
list operations. only)
MaxQueryLookupFields Single- Gets or sets the Read,
valued, maximum number write
integer of lookup fields that (update
may be included in a only)
list item query.
MaxSizeForSelfServiceEvalSiteCreationMB Single- Gets or sets the Read,
valued, maximum possible write
LargeInte size (in MB) of a site (update
ger collection for which only)
the creation of
evaluation sites is
permitted through
self-service.
MaxUniquePermScopesPerList Single- Gets or sets the Read,
valued, maximum number write
integer unique scopes that (update
email.
SendSiteUpgradeEmails Single- Gets or sets Read,
valued, whether to send an write
Boolean email notification (update
once a site upgrade only)
completes.
SendUnusedSiteCollectionNotifications Single- Gets or sets Read,
valued, whether to sent write
Boolean notifications to the (update
owners of unused only)
sites.
ShowStartASiteMenuItem Single- Gets or sets Read,
valued, whether the Start a write
Boolean new site menu (update
command is only)
available.
ShowURLStructure Single- Gets or sets Read,
valued, whether the users write
Boolean are allowed to see (update
the file structure of only)
the websites.
StorageMetricsProcessingDuration Single- Gets or sets the Read,
valued, maximum duration write
integer (in second) for the (update
processing of metric only)
changes for
documents.
SuiteBarBrandingElementHtml Single- Gets or sets the Read,
valued, HTML snippet that is write
string displayed in the (update
SuiteBarBrandingEl only)
ement control.
SyndicationEnabled Single- Gets or sets Read,
valued, whether syndication write
Boolean is enabled. (update
only)
TypeName Single- Gets the type of Read
valued, object for the web
string application.
UnthrottledPrivilegedOperationWindowEna Single- Gets or sets Read,
bled valued, whether to enable write
Boolean unthrottled daily (update
time window. When only)
this attribute is set
to TRUE, large list
operations are not
throttled when they
occur within the
time window.
UnusedSiteNotificationPeriod Single- Gets the time period Read
valued, during which the
string site was unused.
(
TimeSpan)
UnusedSiteNotificationsBeforeDeletion Single- Gets or sets the Read,
valued, number of site write
integer deletion (update
notifications that only)
must be sent before
an unused site gets
deleted.
UpgradeEvalSitesRetentionDays Single- Gets or sets the Read,
valued, period (in days) write
integer since the evaluation (update
site creation date only)
after which the
evaluation site gets
deleted.
UpgradeMaintenanceLink Single- Gets or sets a link Read,
valued, pointing to the write
string upgrade (update
maintenance page. only)
UpgradeReminderDelay Single- Gets or sets the Read,
valued, number of days by write
integer which the site (update
collection only)
administrator can
string
UserLicensingId Single- Gets the per-user Read
valued, license.
string
VisibilityFeatureDependencyId Single- Gets the GUID of the Read
valued, feature on which the
string web template depends.
Feature Supported
Password synchronization No
Specifies whether you can synchronize user passwords from an Active
Directory (AD) domain to the connected data system.
ClientPolicy Yes No No No
Allows you to work with client policies in Skype
for Business Online. You can use client policies
to determine the features of Skype for
Business Online that are available to users.
For more information on what data you can
read and write, see ClientPolicy object
attributes.
ConferencingPolicy Yes No No No
Allows you to work with conferencing policies
in Skype for Business Online. You can use
conferencing policies to determine the
features available to the users participating in
a conference.
For more information on what data you can
read and write, see ConferencingPolicy object
attributes.
attributes.
Domain Yes No No No
Allows you to retrieve information about
domains in Microsoft 365.
For more information on what data you can
retrieve, see Domain object attributes.
ExternalAccessPolicy Yes No No No
Allows you to work with external access
policies in Skype for Business Online.
For more information on what data you can
read and write, see ExternalAccessPolicy
object attributes.
HostedVoicemailPolicy Yes No No No
Allows you to work with voice mail policies in
Skype for Business Online.
For more information on what data you can
read and write, see HostedVoicemailPolicy
object attributes.
LicensePlanService Yes No No No
Allows you to retrieve information related to
the license plans and services that are
currently in use in Microsoft 365.
For more information on what data you can
read and write, see LicensePlanService object
attributes.
PresencePolicy Yes No No No
Allows you to work with presence policies in
Skype for Business Online.
For more information on what data you can
read and write, see PresencePolicy object
attributes.
SPOWebTemplate Yes No No No
Allows you to work with web templates in
SharePoint Online.
For more information on what data you can
read and write, see SPOWebTemplate object
attributes.
VoicePolicy Yes No No No
Allows you to read or write data related to
voice policies in Skype for Business Online.
For more information on what data you can
read and write, see VoicePolicy object
attributes.
CustomAttribute3
CustomAttribute4
CustomAttribute5
CustomAttribute6
CustomAttribute7
CustomAttribute8
CustomAttribute9
CustomAttribute10
CustomAttribute11
CustomAttribute12
CustomAttribute13
CustomAttribute14
CustomAttribute15
ExtensionCustomAttribute4
ExtensionCustomAttribute5
address. Write
Fax Gets or sets the fax number of the Read,
contact. Write
FirstName Gets or sets the first name of the mail- Read,
enabled contact. Write
GrantSendOnBehalfTo Gets or sets the distinguished name Read,
(DN) of other senders that can send Write
messages on behalf of the contact.
This reference attribute only accepts the
following object type:
l Mailbox
contact. Write
StreetAddress Gets or sets the street address of the Read,
contact. Write
TelephoneAssistant Gets or sets the phone number of the Read,
contact’s assistant. Write
Title Gets or sets the title of the contact. Read,
Write
UMCallingLineIds Gets or sets telephone numbers or Read,
telephone extensions that can be Write
mapped to the contact if it has Unified
Messaging enabled.
To specify multiple telephone numbers
use a comma as a separator.
This attribute only accepts values that
have less than 128 characters.
UMDtmfMap Gets or sets whether to create a user- Read,
defined DTMF map for the contact if it Write
has Unified Messaging enabled.
UseMapiRichTextFormat Gets or sets a format for the MAPI Rich Read,
Text Format messages sent to the Write
contact.
This attribute can take one of the
following values:
l Never: Specifies to convert all
messages sent to the contact to
the plain text format.
l Always: Specifies to always use
the MAPI Rich Text Format (RTF)
for the messages sent to the
contact.
l UseDefaultSettings: Specifies to
use the message format set in the
MAPI client that sent the message
to the contact.
UsePreferMessageFormat Gets or sets whether the message Read,
format specified for the contact Write
group.
This attribute can take senders in any of
the following formats:
l Alias
l Canonical DN
l Display name
l Distinguished name (DN)
l Domain\account
l GUID
l Immutable ID
l Legacy Exchange DN
l SMTP address
l User principal name
CustomAttribute3
CustomAttribute4
CustomAttribute5
CustomAttribute6
CustomAttribute7
CustomAttribute8
CustomAttribute9
CustomAttribute10
CustomAttribute11
CustomAttribute12
CustomAttribute13
CustomAttribute14
CustomAttribute15
ExtensionCustomAttribute4
ExtensionCustomAttribute5
following values:
l TRUE: Specifies to ignore the
applicable naming policy.
l FALSE: Specifies to use the
applicable naming policy.
IsSecurity Gets or sets whether the distribution Read,
group is a security distribution group. Write
NOTE:
This
attribute
allows
you to
write
data
only
when
you use
the
Microsof-
t 365
Connect-
or to
perform
a create
opera-
tion in
Microsof-
t 365.
MailTip Gets or sets the message displayed to Read,
senders when they start writing an Write
email message to the distribution
group.
MailTipTranslations Gets or sets the MailTip message Read,
translations in additional languages. Write
This attribute accepts the following
format:
<LanguageLocale>:<MailTipMessageTran
slation>
ConditionalCustomAttribute1
0
ConditionalCustomAttribute1
1
ConditionalCustomAttribute1
2
ConditionalCustomAttribute1
3
ConditionalCustomAttribute1
4
ConditionalCustomAttribute1
5
distribution group.
A comma that
separates values of this
multivalued attribute
acts as the OR
operator.
CustomAttribute1 Get or set the Read, Write
additional custom
CustomAttribute2
values you specify.
CustomAttribute3
CustomAttribute4
CustomAttribute5
CustomAttribute6
CustomAttribute7
CustomAttribute8
CustomAttribute9
CustomAttribute10
CustomAttribute11
CustomAttribute12
CustomAttribute13
CustomAttribute14
CustomAttribute15
distinguished name
(DN) of other senders
that can send
messages on behalf of
the dynamic
distribution group.
This reference attribute
only accepts the
following object type:
l Mailbox
distribution group.
To specify multiple
users, use a comma as
a separator.
This reference attribute
is required if you set
the value of the
ModerationEnabled
attribute to TRUE.
This reference attribute
accepts the following
object types:
l Mailbox
l MailUser
dynamic distribution
group. You can use this
attribute if the group
has two or more SMTP
email addresses.
RecipientContainer Gets or sets the Read, Write
recipients used to build
the dynamic
distribution group,
based on their location
in Active Directory.
This attribute can take
the canonical name of
the Active Directory
Organizational Unit
(OU) or domain where
the recipients reside.
When this attribute is
omitted, the local
container is used.
RecipientFilter Gets or sets the mail- Read, Write
enabled recipients to be
When writing data using this
included in the dynamic
attribute, you cannot use any
distribution group. This
of the following attributes to
attribute accepts
write data:
OPATH filtering syntax.
l IncludedRecipients
Syntax example:
l ConditionalCompany
((Company -eq
'MyCompany') -and l ConditionalCustomAttrib
(City -eq 'London')) ute<Number>
l ConditionalDepartment
l ConditionalStateOrProvi
nce
formats:
l Alias
l Canonical DN
l Display name
l Distinguished
name (DN)
l Domain\account
l GUID
l Immutable ID
l Legacy Exchange
DN
l SMTP address
l User principal
name
name
reports are
enabled.
l FALSE (default):
Indicates that
delivery reports
are disabled.
SendModerationNotifications Gets or sets whether or Read, Write
not to send a
notification to the
sender whose message
to the moderated
dynamic distribution
group is rejected by a
moderator.
This attribute can take
one of the following
values:
l Always:
Indicates that
moderation
notifications are
sent to all
senders.
l Internal:
Indicates that
moderation
notifications are
sent to the
internal senders
only.
l Never: Indicates
that moderation
notifications are
disabled.
SendOofMessageToOriginatorE Gets or sets a value Read, Write
nabled that specifies whether
or not to deliver out-of-
office messages to the
user who sent an e-
mail message to the
dynamic distribution
group.
DD.HH:MM:SS
The maximum value this attribute can
accept is 24855.03:14:07
Example 1
30.05:00:00
Specifies to retain the mailbox audit
logs for 30 days and 5 hours.
Example 2
00.00:00:00
The mailbox audit logs are never
deleted.
BypassModerationFromSendersOrMe Gets or sets the senders whose Read,
mbers messages bypass moderation for the Write
mailbox.
This reference attribute can take any of
the following values for the senders:
l DN
l Canonical name
l GUID
l Name
l Display name
l Legacy Exchange DN
l Primary SMTP email address
CustomAttribute3
CustomAttribute4
CustomAttribute5
CustomAttribute6
CustomAttribute7
CustomAttribute8
CustomAttribute9
CustomAttribute10
CustomAttribute11
CustomAttribute12
CustomAttribute13
CustomAttribute14
CustomAttribute15
ExtensionCustomAttribute4
ExtensionCustomAttribute5
Example
10.00:00:00
Specifies to retain deleted items for 10
days 00 hours 00 minutes and 00
seconds.
RetentionComment Gets or sets a comment on user’s hold Read,
status. This comment is displayed in Write
Outlook.
You can only write the value of this
attribute if the value of the
RetentionHoldEnabled attribute is set to
TRUE.
RetentionHoldEnabled Gets or sets whether retention hold is Read,
enabled for messaging retention Write
policies.
This attribute can take one of the
following values:
l TRUE
l FALSE
in this attribute.
RulesQuota Gets or sets the limit for the size of rules Read,
for the mailbox. Write
Qualify the value you specify in this
attribute by appending B (bytes) or KB
(kilobytes). Unqualified values are
treated as bytes. The maximum value
this attribute accepts is 256 KB.
SecondaryAddress Sets the secondary address used by the Write
UM-enabled user.
SecondaryDialPlan Sets a secondary UM dial plan to use. Write
SendModerationNotifications Gets or sets whether to send status Read,
notifications to users when a message Write
they sent to the moderated distribution
group is rejected by a moderator.
This attribute can take one of the
following values:
l Always: Specifies that
notifications are sent to all
senders.
l Internal: Specifies that
notifications are only sent to the
internal senders in your
organization.
l Never: Specifies that all status
notifications are disabled.
SharingPolicy Gets or sets the sharing policy Read,
associated with the mailbox. Write
SimpleDisplayName Gets or sets an alternate description of Read,
the mailbox in a situation where a Write
limited set of characters is allowed. The
limited set of characters includes ASCII
characters 26 through 126.
SingleItemRecoveryEnabled Gets or sets whether to enable or Read,
disable the purging of recovery items. Write
This attribute can take one of the
following values:
l TRUE: Specifies to disable the
purging of recovery items.
l FALSE: Specifies to enable the
purging of recovery items.
UMDtmfMap Gets or sets whether to create a user- Read,
defined DTMF map for the user if it has Write
Unified Messaging enabled.
UsageLocation Gets a two-letter country code that Read
defines the location of the user. Usage
location determines the services
available to the user.
For example:
l FR
l GB
l NL
UserCertificate Gets or sets the digital certificate used Read,
to sign email messages of the user. Write
UserPrincipalName Gets or sets the logon name of the Read,
mailbox user. Write
UserSMimeCertificate Gets or sets the SMIME certificate used Read,
to sign email messages of the user. Write
CustomAttribute3
CustomAttribute4
CustomAttribute5
CustomAttribute6
CustomAttribute7
CustomAttribute8
CustomAttribute9
CustomAttribute10
CustomAttribute11
CustomAttribute12
CustomAttribute13
CustomAttribute14
CustomAttribute15
ExtensionCustomAttribute4
ExtensionCustomAttribute5
<LanguageLocale>:<MailTipMessageTran
slation>
A MailTip message translation cannot
exceed 250 characters.
MessageBodyFormat Gets or sets the message body format Read,
for messages sent to the mail user. Write
The values this attribute can take
depend on the value in the
MessageFormat attribute.
When the value in the MessageFormat is
Mime, the MessageBodyFormat attribute
can take the following values:
l Text
l Html
l TextAndHtml
Members Gets the users who have been assigned the Read
policy.
ObjectID Gets the unique object identifier (GUID). Read
These attributes allow you to get or set the license plans and services available to the user
in Microsoft 365. The attributes support Read and Write operations.
The names and display names of these attributes are formed dynamically according to the
following patterns:
If necessary, you can modify the display names of Microsoft 365 license plans and services
that appear in the Synchronization Service Console. These display names are part of the
Office 365 Connector schema and saved in the O365LicensePlansServices.xml file located
Other attributes
LastName Gets or sets the last name of the user. Read, Write
LiveID Gets the user’s unique login ID. Read
MailboxId Gets the GUID of the user’s mailbox. Read
Manager Gets or sets the name of the user’s Read, Write
manager.
MobilePhone Gets or sets the user’s mobile phone Read, Write
number.
Name Gets or sets the name of the user. Read, Write
Notes Gets or sets notes about the user. Read, Write
ObjectID Gets the unique object identifier (GUID). Read
Office Gets or sets the user’s office. Read, Write
OtherFax Gets or sets the alternate fax number of Read, Write
the user.
OtherHomePhone Gets or sets the alternate home phone Read, Write
number of the user.
OtherTelephone Gets or sets the alternate phone number Read, Write
of the user.
Pager Gets or sets the pager of the user. Read, Write
Password Sets a password for the user. Write
PasswordNeverExpires Gets or sets whether or not the user’s Read, Write
password periodically expires.
This attribute can take one of the
following values:
l TRUE (default): Specifies that the
user’s password never expires.
l FALSE: Specifies that the user’s
password periodically expires.
Phone Gets or sets the phone number of the Read, Write
user.
PhoneNumber Gets or sets the user’s phone number. Read, Write
PhoneticDisplayName Gets or sets a phonetic pronunciation of Read, Write
the value specified in the DisplayName
attribute for the user.
PostalCode Gets or sets the user’s postal code. Read, Write
PostOfficeBox Gets or sets the post office box number of Read, Write
the user.
PreferredLanguage Gets or sets the preferred language for Read, Write
the user.
RemotePowerShellEnabled Gets or sets whether remote Windows Read, Write
PowerShell cmdlets are available to the
user.
This attribute can take one of the
following values:
l TRUE
l FALSE
ResetPasswordOnNextLogon Gets or sets whether the user must reset Read, Write
their password at next logon.
This attribute can take one of the
following values:
l TRUE
l FALSE
SimpleDisplayName Gets or sets an alternate description of Read, Write
the user in a situation where a limited set
of characters is allowed.
The limited set of characters includes
ASCII characters from 26 to 126.
State Gets or sets the state where the user is Read, Write
located.
StateOrProvince Gets or sets the state or province of the Read, Write
user.
StreetAddress Gets or sets the user’s street address. Read, Write
Title Gets or sets the user’s title. Read, Write
UMDtmfMap Gets or sets whether to create a user- Read, Write
defined DTMF map for the user if it has
Unified Messaging enabled.
UsageLocation Gets or sets the two-letter ISO country Read, Write
designation. This attribute specifies the
user’s country where services are
consumed.
UserPrincipalName Gets or sets the user’s Microsoft Online Read, Write
Services ID.
WebPage Gets or sets the web page address of the Read, Write
user.
WindowsEmailAddress Gets or sets the email address of the user Read, Write
stored in Active Directory.
CustomAttribute3
CustomAttribute4
CustomAttribute5
CustomAttribute6
CustomAttribute7
CustomAttribute8
CustomAttribute9
ExtensionCustomAttribute4
ExtensionCustomAttribute5
Feature Supported
Password synchronization No
Specifies whether you can synchronize user passwords from an Active
Directory (AD) domain to the connected data system.
$Id = “<ClientId>”
Connect-AzureAD
# Get the required role ID from the Active Roles Azure AD Connector
Application and save it to the $roleId variable
The following sections describe the attributes provided by the Microsoft Azure AD
Connector. By using these attributes, you can read and/or write data related to a particular
object in Microsoft Azure Active Directory.
This means that although these user attributes are visible, they cannot be set in a
mapping rule.
This means that although these group attributes are visible, they cannot be set in a
mapping rule.
NOTE: Consider the following when planning to configure a connection with the
SCIM Connector:
l The SCIM Connector is tested to support the Starling Connect PingOne and
Workday HR connectors. To configure a connection for import-based workflows to
the SCIM 2.0-based SuccessFactors HR 8.0 or ServiceNow 2.0 Starling connectors,
use the Generic SCIM Connector instead. For more information, see Configuring
data synchronization with the Generic SCIM Connector.
l The SCIM Connector supports only the standard schema of the SCIM protocol. It
does not support extended schemas, and therefore cannot handle user-made
custom attributes.
For the list of Active Roles Synchronization Service connector features that the SCIM
Connector supports or does not support, see the following table.
Feature Supported
Bidirectional synchronization No
Specifies whether you can both read and write data in the connected data
system.
Password synchronization No
Specifies whether you can synchronize user passwords from an Active
Directory (AD) domain to the connected data system.
For more information on the SCIM protocol, see the official SCIM site, or the following IETF
RFC documents:
For the list of Active Roles Synchronization Service connector features that the Generic
SCIM Connector supports or does not support, see the following table.
Feature Supported
Bidirectional synchronization No
Specifies whether you can both read and write data in the connected data
system.
Password synchronization No
Specifies whether you can synchronize user passwords from an Active
Directory (AD) domain to the connected data system.
For more information on the SCIM protocol, see the official SCIM site, or the following IETF
RFC documents:
Prerequisites
Before configuring the connection, make sure that the following conditions are met:
l Your organization must have an active Starling Connect account.
l The Starling connector to which you want to connect must be already configured in
Starling Connect.
l If your organization is using a proxy server for outbound connections, make sure that
the system level proxy settings are properly configured.
To configure system-level proxy settings, navigate to one of the following Windows
configuration pages:
l Control Panel > Internet Settings > Connections > LAN Settings
l Settings > Network and Internet > Proxy
l You are aware of the specific implementation details (such as the supported objects
and operations) of the Starling Connect connector you want to connect to. For more
information, see the connector-specific sections of the Starling Connect Active Roles
Administration Guide.
3. (Optional) If you want to use a remote connector for the configured connection,
configure Remote connector access as described in Creating a connection using a
remotely installed connector. To continue, click Next.
4. To continue, click Next.
The Connection settings step of the Generic SCIM Connector appears.
5. Under General settings, specify the base SCIM URL of the Starling Connect
connector to which you want to connect.
TIP: To check the base SCIM URL of the Starling Connect connector, in Starling
Connect, navigate to Connectors > Active Connectors, select the SCIM-
based connector to which you want to connect, then copy the value of the
SCIM URL property.
6. Under Authentication settings, to enable the authentication scheme options
required by the supported Starling Connect connectors, select the Starling
authentication scheme, then configure the following settings:
l Token endpoint URL: Specifies the full path of the Starling connector
token endpoint.
TIP: To find the token endpoint URL of the Starling Connect connector, in
Starling Connect, navigate to Connectors > Active Connectors, and copy
the value of the SCIM Token Endpoint URL property.
l Client ID: Specifies the SCIM client ID.
TIP: To find the SCIM client ID of the Starling Connect connector, in Starling
Connect, navigate to Connectors > Active Connectors, and copy the value
of the SCIM Client ID property.
l Client secret: Specifies the SCIM client secret.
TIP: To find the SCIM client secret of the Starling Connect connector, in
Starling Connect, navigate to Connectors > Active Connectors, and copy
the value of the Show SCIM Client Secret text box.
7. Under Implementation plugin, to enable the pre-made connection implementation
for the supported Starling Connect connectors, select Starling batch 1 - v2.0.
NOTE: The Starling batch 1 - v2.0 implementation plugin is backwards compat-
ible with Starling batch 1 - v1.0, originally released in Active Roles 7.6.1.
The Generic SCIM Connector was tested with the following Starling Connect
connectors:
After Active Roles Synchronization Service created the connection, you can use it to
configure SCIM-based data synchronization by setting up one or more mapping rules and
synchronization workflows.
Creating a connection
To create a connection
For information on the options you can use in the subsequent steps of the wizard, see the
section for the connector you have selected.
Renaming a connection
You can rename any existing data connection in the Active Roles Synchronization
Service Console.
To rename a connection
To synchronize identity data between connected data systems, you can use sync workflows
and synchronization steps. A sync workflow is a set of data synchronization operations
called synchronization steps. A sync workflow can include one or more steps. Each
synchronization step defines a synchronization operation to be run between the source and
target connected data systems. To manage sync workflows and their steps, you can use the
Sync Workflows in the Synchronization Service Console.
You can configure a synchronization step to perform one of the following operations:
l Creation: Creates objects in the target data system based on the changes made to
specific objects in the source data system. When creating a new object in the target
data system, Synchronization Service generates initial values for the object
attributes using the attribute population rules you have configured.
l Update: Modifies object attributes in the target data system based on the changes
made to specific objects in the source data system. To specify the objects that will
participate in the update operation you can use object mapping rules. For more
information, see Mapping objects.
l Deprovision: Modifies or removes objects in the target data system after their
counterparts have been disconnected from the source data system. Synchronization
Service can be configured to remove target objects permanently or change them to a
specific state. To specify the objects that will participate in the deprovision operation
you can use object mapping rules. For more information, see Mapping objects.
To synchronize identity data between two data systems, you need to create a sync
workflow, populate the workflow with synchronization steps, and then run the sync
workflow manually or schedule the sync workflow run. The following figure illustrates how
Synchronization Service synchronizes identity data in connected data systems:
Running a sync workflow causes Synchronization Service to read data in the source and
target data systems according to the settings in the sync workflow steps and prepare a list
of changes to be made in the target system. Then, you can commit these changes to the
target data system.
Running a sync workflow manually allows you to review a list of changes before committing
them to the target data system. A scheduled sync workflow run always commits changes to
the target data system automatically.
You can configure as many sync workflows as needed, each performing its own set of
synchronization steps.
You can modify the settings of an existing synchronization step. For more information, see
Modifying an existing sync workflow step.
You can modify the settings of an existing synchronization step. For more information, see
Modifying an existing sync workflow step.
You can modify the settings of an existing synchronization step. For more information, see
Modifying an existing sync workflow step.
General Options
The general options allow you to rename the step, specify a method for processing data in
the source and target connected systems, and specify conditions to stop data processing.
This tab has the following elements:
l Step name: Allows you to rename the step.
l Specify how to process data in connected systems: Allows you to select how to
process data during synchronization. The available methods are the following:
l Process all data: Each run of the step will process all data in the configured
synchronization scope.
l Process delta from last run: Each run of the step will process only the data
that has changed in the configured synchronization scope since the last run.
l Stop data processing if: Allows you to specify conditions that will stop data
processing in the source and target data systems when met.
Source
The Source setting allows you to view information about the source connected system and
source object type specified for the synchronization step. You can also view or modify the
criteria used to perform the creation, deprovision, or update operation in the step.
For all types of synchronization steps (creating, deprovisioning, and updating), this tab
provides the following options:
l Source connected system: Displays the name of the source data system.
l Source object type: Displays the object type that is used as a source for the
synchronization step.
Target
The Target setting allows you to view information about the target connected system and
target object type specified for the synchronization step. For creating steps, you can use
this tab to view and modify the target container to which objects are created and rules to
generate unique names for created objects.
For all types of synchronization steps (creating, deprovisioning, and updating) this tab
provides the following elements:
l Target connected system: Displays the name of the data system that is currently
used as a target for the synchronization step.
l Target object type: Displays the object type that is currently used as a target for
the synchronization step.
For creating steps related to certain types of target data systems, this tab may also provide
any of the following additional elements:
l Target container: Allows you to specify the target data system container in which
you want to create objects from the source data system. For more information, see
Generating object names by using rules.
l Rules to generate unique object name: Allows you to set up a list of rules to
generate a unique name for each object being created. For more information, see
Generating object names by using rules.
Creation Rules
Creation rules allow you to view or modify the rules used for creating objects. This tab has
the following elements:
You can use this tab to import or export initial attribute population rules.
1. In the list of configured attribute population rules, select the rule you want to export.
2. Click More, then click Export.
3. In the Save As dialog, specify an XML file to store the rule.
1. Expand Initial Attribute Population Rules, click More, then click Import.
2. Use the Open dialog to open the XML file that stores the population rule to import.
Deprovisioning Rules
Deprovisioning rules allow you to select a method for deprovisioning synchronized objects.
As part of deprovisioning, you can either delete the target objects if the source objects
meet the synchronization criteria configured in the wizard, or just modify the target objects
using the following deprovisioning rules.
l Rules to Modify Object Attributes: Allows you to set up a list of rules to modify
object attributes in the target data system. For more information, see Modifying
attribute values by using rules.
l Rules to Move Objects: Expand this option to specify the location to which you
want to move objects. Click the down arrow on the button, and then select one of
the following:
l Browse: Click to locate and select a single target container.
l PowerShell Script: Click to compose a PowerShell script that calculates the
target container name.
l Rule: Click to configure a set of rules for selecting target containers.
l Use Mapping: Click to define a target container based on the mapping of the
source object.
l Clear: Click to use an empty value.
l Rules to Rename Objects: Allows you to view or change the list of rules used to
rename target objects. For more information, see Generating object names by
using rules.
Step Handlers
Step handlers allow you to create, modify, or delete handlers for a sync workflow. For more
information on how to use step handlers, see Using sync workflow step handlers. This tab
has the following elements:
l Add handler: Starts a wizard that helps you add a new handler for the sync
workflow step. By default, the wizard creates a new handler that runs your
PowerShell script.
l Disable: Disables the step handler.
l Enable: Enables the step handler.
l Move up: Moves the step handler one position up in the list.
l Move down: Moves the step handler one position down in the list.
l Delete: Deletes the step handler.
1. Click the down arrow on the leftmost button provided below the Rules to generate
unique object name list.
2. Select a list item:
l Attribute: Allows you to select the target object attribute whose value you
want to use as the object name.
l Rule: Allows you to configure a rule to generate target object names. For
details, see Using value generation rules.
l PowerShell Script: Allows you to type a PowerShell script to generate target
object names.
When the Rules to generate unique object name list includes two or more entries,
Synchronization Service uses the uppermost rule in the list to generate the target object
name. If the generated object name is not unique, Synchronization Service uses the next
rule in the list, and so on.
1. In the Rules to generate unique object name list, right-click a rule, then select
Copy from the shortcut menu.
2. In the rules list, right-click an entry, then select Paste from the shortcut menu.
Once you have explicitly selected an attribute in this option, you can click the Advanced
link to configure some advanced synchronization settings for the attribute.
For example, you can specify which characters to retrieve from the attribute value, how to
modify the retrieved value (remove white-space characters or change the capitalization),
or set how to process references in the attribute. The available settings depend on the
attribute types selected in the Source item and Target item options.
Once you have explicitly selected an attribute in this option, you can click the Advanced
link to configure some advanced synchronization settings for the attribute.
For example, you can select how to handle the existing attribute value (overwrite or
append data to the value) or set how to process references in the attribute. The
available settings depend on the attribute types selected in the Source item and
Target item options.
Once you have explicitly selected an attribute in this option, you can click the Advanced
link to configure some advanced synchronization settings for the attribute.
For example, you can select how to handle the existing attribute value (overwrite or
append data to the value) or set how to process references in the attribute. The
available settings depend on the attribute types selected in the Source item and
Target item options.
Once you have explicitly selected an attribute in this option, you can click the Advanced
link to configure some advanced synchronization settings for the attribute.
For example, you can specify which characters to retrieve from the attribute value, how to
modify the retrieved value (remove white-space characters or change the capitalization),
or set how to process references in the attribute. The available settings depend on the
attribute types selected in the Source item and Target item options.
When running a sync workflow step that has a merge sync rule configured for the first time,
Synchronization Service synchronizes attribute values from the source to the target. In
each subsequent run of the sync workflow step, the synchronization direction depends on
which attribute value (source or target) is more recent, as follows:
1. Click Add.
2. Configure the rule entry as appropriate. For more information, see Configuring
a rule entry.
1. From the Rule entries list, select the entry you want to modify, then click Edit.
2. Configure the rule entry as appropriate. For more information, see Configuring
a rule entry.
1. Follow the procedure of the Adding a creating step section until you reach the
Specify creation rules page.
2. In the Initial Attribute Population Rules element, click the down arrow on the
leftmost button below the list to select Forward Sync Rule.
3. In the dialog that opens, add the following pair of attributes:
l Source item: member attribute (Active Directory)
l Target item: member attribute (AD LDS)
For more information about the options in this dialog, see Configuring a
forward sync rule.
4. When you are finished, click OK.
5. Follow the steps in the wizard to complete the creating step.
1. Follow the procedure of the Adding a creating step section until you reach the
Specify creation rules page.
2. In the Initial Attribute Population Rules element, click the down arrow on the
leftmost button below the list to select Forward Sync Rule.
3. In the dialog that opens, add the following pair of attributes:
l Source item: otherTelephone attribute (Active Directory)
l Target item: otherTelephone attribute (AD LDS)
For more information about the options in this dialog, see Configuring a
forward sync rule.
4. When you are finished, click OK.
5. Follow the steps in the wizard to complete the configuration of the creating step.
To delete an alert
To create a profile
1. Click Add below the list of profiles, then specify the settings you want to use. For the
descriptions of the settings you can specify, see Outgoing mail profile settings.
2. When you are finished, click OK.
1. In the list, select the outgoing mail profile you want to edit.
2. Click Edit below the list of profiles, then specify the settings you want to use. For the
description of the settings you can specify, see Outgoing mail profile settings.
3. When you are finished, click OK.
To delete a profile
1. In the list, select the outgoing mail profile you want to delete.
2. Click the Delete button below the list of profiles.
Mapping objects
Object mapping allows you to establish one-to-one relationships between objects in two
connected data systems. By using object mapping, you can determine what objects will
participate in data synchronization operations you run between these two data systems.
Synchronization Service maps objects automatically when running the creating steps of a
sync workflow. In this case, a one-to-one relationship is automatically established between
source objects and their counterparts created in the target connected system during the
creation operation. In some cases, however, you may have to manually map objects. For
example, you should configure object mapping before running a sync workflow that
includes updating or deprovisioning steps. By doing so, you provide Synchronization
Service with the information on which objects need to be updated or deprovisioned in the
target data system.
To map objects, you can use mapping pairs and mapping rules. A mapping pair allows you
to establish a relationship between a certain object type in one connected system and its
counterpart in the other connected system. A mapping rule allows you to define the scope
of conditions where the objects belonging to the object types specified in a particular
mapping pair will be mapped. You can create multiple mapping rules for a mapping pair,
with each mapping rule defining a specific mapping condition. You have to run your
mapping rules for them to take effect. After you run a mapping rule, Synchronization
Service reads data in the connected data systems for which the rule is configured, and then
maps the objects that meet the conditions specified in the mapping rule.
The following example shows how a mapping rule works:
In this example, one-to-one relationship is established between the user object John
Malcolm in Connected System 1 and the user object John Doe in Connected System
2: the first names of these user objects match, and thus the condition specified in the
mapping rule is met. Now, if you configure a sync workflow for these systems and
populate it with synchronization steps, identity information will be synchronized between
these two user objects, since they are mapped. The direction of synchronization depends
on which of these two connected data systems acts as the synchronization source and
which is the target.
This method allows you to run your mapping rules without creating a recurring schedule.
Running mapping rules on a recurring schedule allows you to properly map newly-created
Active Directory user objects to their counterparts in the connected systems where you
automatically synchronize passwords with the Active Directory domain. If you do not run
mapping rules on a regular basis, some passwords may become out of sync due to the
changes that inevitably occur to your environment. For example, new user objects are
created, some user objects are deleted, but Synchronization Service cannot detect these
changes and synchronize passwords for the newly-created users before you apply the
mapping rules. In this scenario, the best way to ensure Synchronization Service
synchronizes all passwords is creating a recurring schedule for applying your mapping rules
on a regular basis.
To unmap objects
Automated password
synchronization
If your enterprise environment has multiple data management systems, each having its
own password policy and dedicated user authentication mechanism, you may face one or
more of the following issues:
l Because users have to remember multiple passwords, they may have difficulty
managing them. Some users may even write down their passwords. As a result,
passwords can be easily compromised.
l Each time users forget one or several of their numerous access passwords, they have
to ask administrators for password resets. This increases operational costs and
translates into a loss of productivity.
l There is no way to implement a single password policy for all of the data
management systems. This too impacts productivity, as users have to log on to each
data management system separately in order to change their passwords.
With Synchronization Service, you can eliminate these issues and significantly simplify
password management in an enterprise environment that includes multiple data
management systems.
Synchronization Service provides a cost-effective and efficient way to synchronize user
passwords from an Active Directory domain to other data systems used in your
organization. As a result, users can access other data management systems using their
Active Directory domain password. Whenever a user password is changed in the source
Active Directory domain, this change is immediately and automatically propagated to other
data systems, so each user password remains in sync in the data systems at all times.
You need to connect Synchronization Service to the data systems in which you want to
synchronize passwords through special connectors supplied with Synchronization Service.
1. Install Capture Agent on each domain controller in the Active Directory domain you
want to be the source for password synchronization operations.
Capture Agent tracks changes to the user passwords in the source Active Directory
domain and provides this information to Synchronization Service, which in turn
synchronizes passwords in the target connected systems you specify.
For more information on how to install Capture Agent, see Managing Capture Agent.
2. Connect the Synchronization Service to the Active Directory domain where you
installed Capture Agent.
Alternatively, you can configure a connection to Active Roles that manages the
source Active Directory domain.
3. Connect the Synchronization Service to the data system where you want to
synchronize user object passwords with those in the source Active Directory domain.
l For some target data systems (such as SQL Server) you must specify the
data you want to participate in the password synchronization by configuring
an SQL query.
l If the target data system is an LDAP directory service accessed via the
generic LDAP connector, you must specify the target object type for which
you want to synchronize passwords and the attribute where you want to store
object passwords.
4. Ensure that user objects in the source Active Directory domain are properly mapped
to their counterparts in the target connected system.
For more information about mapping objects, see Mapping objects.
Synchronization Service automatically maps objects between the source Active
Directory domain and the target connected system if you configure sync workflows
to manage the creation and deprovision operations between the source Active
Directory domain (or Active Roles that manages that domain) and the target
connected system.
For more information on sync workflows, see Synchronizing identity data.
5. Create a password synchronization rule for the target connected system.
For more information, see Creating a password sync rule.
After you complete the above steps, the Synchronization Service starts to automatically
track user password changes in the source Active Directory domain and synchronize
passwords in the target connected system.
If necessary, you can fine-tune the password synchronization settings by completing these
optional tasks:
1. Use Group Policy Editor to open 1. Use Group Policy Object Editor to
the group policy object linked to open the group policy object linked
the OU holding the domain to the OU holding the 32-bit
controllers on which you want to domain controllers.
install Capture Agent.
2. Do one of the following in the
2. In the Group Policy Object Editor Group Policy Object Editor console
console tree, do one of the tree:
following: l In Windows Server 2016 or
l In Windows Server 2016 or later, expand the Computer
later, expand the Configuration node, then
Computer Configuration expand Policies, and select
node, then expand Software Settings.
Policies, and select
3. In the details pane, click Software
Software Settings.
Installation, on the Action menu
3. In the details pane, click point to New, and then click
Software Installation, on the Package.
Action menu point to New, and
4. Use the dialog to open the
then click Package. SyncServiceCaptureAgent_8.1.3_
4. Use the dialog to open one of the x86.msi file.
following files:
5. In the Deploy Software dialog,
l SyncServiceCaptureAgent_ select Assigned, and then click
3. Run the following command at a command prompt to refresh the Group Policy
settings:
gpupdate /force
1. On the computer where Capture Agent is installed, open the list of installed
programs.
2. In the list of installed programs, select One Identity Active Roles 8.1.3 -
Synchronization Service Capture Agent x64 or One Identity Active Roles
8.1.3 - Synchronization Service Capture Agent x86.
3. To delete Capture Agent, click Uninstall.
4. Follow the on-screen instructions.
Optionally, you can configure a password synchronization rule to modify attribute values of
the target connected system objects whose passwords are being synchronized.
Service
Connection
Point 5
Connection
Point 6
Connection
Point 7
You can modify the default values of these parameters by using Group Policy and the
Administrative Template supplied with the Synchronization Service. The next steps assume
that all the domain controllers where the Capture Agent is installed are held within
organizational units.
You can modify the Synchronization Service parameters using Group Policy and the
Administrative Template supplied with Synchronization Service.
1. On the computer running the Synchronization Service, start Group Policy Object
Editor, and then connect to the Local Computer Policy Group Policy object.
2. In the Group Policy Object Editor console, expand the Local Computer
Policy node, expand the Computer Configuration node, and select
Administrative Templates.
3. On the Action menu, point to All Tasks, and click Add/Remove Templates.
This section illustrates how to use a custom certificate for encrypting the password
synchronization traffic in Windows Server 2012.
This section provides steps to request certificates using the Windows Server 2012
Certificate Services web interface. For detailed information about the Certificate Request
Wizard, refer to the documentation on Certification Authority.
After you install the certificate, it becomes available in the Certificates snap-in, in the
Personal > Certificates store.
1. On the computer where you installed the certificate in the Obtaining and installing
a certificate step, open the Certificates - Local Computers snap-in.
2. In the Console tree, expand the Personal > Certificates store.
3. In the details pane, click the issued certificate you want to export.
4. On the Action menu, point to All Tasks, and then click Export.
You will need the copied thumbprint value to configure the Capture Agent and
Synchronization Service.
For instructions on how to add an administrative template file to a Group Policy object, see
Adding an administrative template to Group Policy object.
1. In the Group Policy Object Editor console, expand the Group Policy object, and then
expand the Computer Configuration node.
2. Expand the Administrative Templates > Active Roles node to select Sync
Service Capture Agent Settings.
3. In the details pane, double-click Certificate to encrypt Capture Agent traffic.
1. On the computer running the Synchronization Service, start Group Policy Object
Editor, and then connect to the Local Computer Policy Group Policy object.
2. In the Group Policy Object Editor console, expand the Local Computer
Policy node, expand the Computer Configuration node, and select
Administrative Templates.
3. On the Action menu, point to All Tasks, and click Add/Remove Templates.
4. In the Add/Remove Templates dialog, click Add, and then use the Policy
Templates dialog to open the SyncService.adm file that holds the
Administrative Template.
5. By default, the SyncService.adm file is stored in <Active Roles installation
folder>\SyncServiceCaptureAgent\Administrative Templates.
6. Under Computer Configuration > Administrative Templates > Active Roles,
select Sync Service Settings.
7. In the details pane, double-click Certificate to encrypt Capture Agent traffic.
8. Select the Enabled option, and then paste the certificate’s thumbprint (the one you
copied in Copying the certificate's thumbprint) in the Thumbprint text box. When
finished, click OK.
9. For the changes to take effect, refresh the Group Policy settings by running the
following command at a command prompt:
gpupdate /force
Synchronization history
Synchronization Service Console provides the Synchronization History option that allows
you to view the details of completed synchronization workflow runs, password
synchronization rule runs, and map and unmap operations.
The synchronization history also helps you troubleshoot synchronization issues by
providing information on the errors that were encountered during sync workflow runs,
password sync rule runs, or map and unmap operations.
You can also selectively clean up entries from the synchronization history.
To access the synchronization history, use the Sync History tab in the Synchronization
Service Console.
You can click a sync workflow run entry in the list to view detailed information about the
sync workflow steps that were run, objects that participated in that run, and errors
encountered during the run, if any.
To view detailed information about the objects that belong to a certain object
category, click the number displayed next to the object category name in the Source
or Target column.
To view detailed information about encountered errors, click the link displaying the
number of errors.
Scenarios of use
This section provides some use case scenarios that help you familiarize yourself with
Synchronization Service. The scenarios illustrate how to create and run sync workflows and
their steps to update and create user information from a Human Resources (HR) database
represented by a delimited text file to an Active Directory domain.
The scenarios are:
l Scenario: Creating users from a .csv file to an Active Directory domain. In this
scenario, Synchronization Service creates user accounts from a Comma Separated
Values (.csv) file that includes a HR database to individual Organizational Units in an
Active Directory domain, depending on the city where each user is based.
l Scenario: Using a .csv file to update user accounts in an Active Directory domain. In
this scenario, Synchronization Service updates user accounts in an Active Directory
domain based on the changes made to the HR database saved in a Comma Separated
Values (.csv) file.
l Scenario: Synchronizing data between One Identity Manager Custom Target
Systems and an Active Directory domain. In this scenario, Quick Connect updates
data in One Identity Manager based on the changes made in Active Directory domain.
l Scenario: Deprovisioning between One Identity Manager Custom Target Systems
and an Active Directory domain. In this scenario, Quick connect deprovisioning
synchronized objects in One Identity Manager processed from the Active
Directory domain.
l Scenario: Provisioning of Groups between One Identity Manager Custom Target
Systems and an Active Directory domain. In this scenario, Quick Connect
provisions group objects to be synchronized to One Identity Manager from Active
Directory domain.
l Scenario: Enabling Delta Sync mode between One Identity Manager Custom Target
Systems and an Active Directory domain. In this scenario, Quick Connect updates
data in One Identity Manager based on the changes made in Active Directory domain
in the delta sync mode.
Before you proceed with these sample scenarios, perform the following steps:
1. Make sure you have properly configured the connection to the target Active Directory
domain in the Synchronization Service Console.
TIP: You can use the Active Directory Users and Computers tool to ensure that Synchron-
ization Service has created user accounts in the Employees OU. The New York, Tokyo,
Amsterdam, and OtherCities OUs may include some disabled user accounts created by
Synchronization Service.
1. In the Synchronization Service Console, open the Sync Workflows tab, and then
click the sync workflow you created in the Creating a sync workflow step.
2. Click Add synchronization step.
3. On the Select an action page, select Creation, and then click Next.
4. On the Specify source and criteria page, click Specify, click Add new
connected system, and then step through the wizard to add the sample Comma
Separated Values (.csv) file as a connected system:
a. Use the Connection name box to type a descriptive name for the connection
being created.
b. In the Use the specified connector list, select Delimited Text File
Connector. Click Next.
c. Click Browse to locate and select the sample Comma Separated Values (.csv)
file supplied with Synchronization Service. This file is located in the
<Synchronization Service installation folder>\Samples folder.
d. Step through the wizard until you are on the Specify attributes to identify
objects page.
e. In the Available attributes list, select Employee ID, click Add, and then
click Finish.
5. Click Next.
6. On the Specify target page, click Specify, and then step through the wizard to add
the target Active Directory domain as a connected system:
a. Use the Connection name box to type a descriptive name for the connection
being created.
b. In the Use the specified connector list, select Active Directory
Connector. Click Next.
c. Use the Domain name field to type the FQDN name of the target Active
$userCity = $srcObj["City"]
switch ($userCity)
{
"New York" {$container = "OU=New York,OU=Employees,DC=mycompany,DC=com";
break}
"Amsterdam" {$container =
"OU=Amsterdam,OU=Employees,DC=mycompany,DC=com"; break}
"Tokyo" {$container = "OU=Tokyo,OU=Employees,DC=mycompany,DC=com";
break}
default {$container = "OU=OtherCities,OU=Employees,DC=mycompany,DC=com";
break}
}
$container
NOTE: Before using the script, change the DC=mycompany",DC=com string as appro-
priate to reflect your environment. For example, if you have created the
Employees OU in the testlab.ttt domain, use the following string:
DC=testlab,DC=ttt.
10. Click the down arrow on the leftmost button provided below the Rules to generate
unique object name list.
11. In the provided list, click Attribute.
12. Select Logon Name, and then click OK. Click Next.
13. Expand Initial Attribute Population Rules, and then create forward sync rules to
synchronize the following pairs of attributes:
For more information on how to create rules, see Modifying attribute values by
using rules.
TIP: To view a list of user accounts to be created in the Employees OU, click the number
next to Objects to be created.
1. In the Synchronization Service Console, open the Sync Workflows tab, and then
click the sync workflow you created in the Creating a sync workflow step.
2. Click Add synchronization step.
3. On the Select an action page, select Update, and then click Next.
4. On the Specify source and criteria page, do the following:
a. Click Specify, click Select existing connected system, and then select the
Comma Separated Values (.csv) file you connected in Scenario: Create users
from a .csv file to an Active Directory domain. Click Finish.
b. Make sure that the object type specified in the Source object type box
is csv-Object.
5. Click Next.
6. On the Specify target page, do the following:
a. Click Specify, and then select the Active Directory domain you connected in
Scenario: Create users from a .csv file to an Active Directory domain.
b. Make sure that the object type specified in the Target object type box is
User (user).
7. Click Next.
8. Expand Rules to Modify Object Attributes, and then create forward sync rules to
synchronize the following pairs of attributes:
For information on how to create rules, see Modifying attribute values by using rules.
9. Click Finish.
TIP: To view a list of user accounts to be updated in the Employees OU, in the update
report, click the number next to Objects to be updated.
To select the One Identity Manager modules, Target Systems, and Containers
1. In the Synchronization Service Console, open the Sync Workflows tab, and then
click the AD to OneIM Sync workflow.
2. Click Add synchronization step.
3. On the Select an action page, select Creation, and then click Next.
4. In the Specify source and criteria dialog, click Specify, click Add new
connected system or Select existing connected system, and then step through
the wizard to add the Active Directory Test AD as a connected system.
5. Click Next.
6. In the Specify target dialog, click Specify.
7. Click Add new connected system or Select existing connected system, and
then step through the wizard to add the target One Identity Manager domain as a
connected system.
8. Click Select, to add the required target object type.
9. In the Select Object Type dialog, select the UNSAccountB object type from the
list of object types and click OK.
1. In the Synchronization Service Console, open the Sync Workflows tab, and then
click the AD to OneIM Sync workflow.
2. Click Provision from Test AD to One Identity Manager Connection.
3. Click Provisioning Rules and then click Initial Attribute Population Rules.
An All changes committed message is displayed. The changes are committed from the
source Active Directory Test AD to the target One Identity Manager.
1. In the Synchronization Service Console, open the Sync Workflows tab, and then
click the AD to OneIM Sync workflow.
2. Click Add synchronization step.
3. In the Select an action dialog, select Deprovision, and then click Next.
4. In the Specify source and criteria dialog, click Specify, click Add new
connected system or Select existing connected system, and then step through
the wizard to add the Active Directory Test AD as a connected system.
5. Specify a deprovisioning criteria by selecting one of the following:
l Source object is deleted or out of synchronization scope
l Source object deprovisioning is initiated in connected system
l Source object meets these criteria - Add the criteria for the source
objects to be deprovisioned in the target system
6. Click Next.
7. In the Specify target dialog, click Specify.
8. Click Add new connected system or Select existing connected system, and
then step through the wizard to add the target One Identity Manager domain as a
connected system.
9. Click Select, to add the required target object type.
10. In the Select Object Type dialog, select the UNSAccountB object type from the
list of object types and click OK.
11. In the Specify deprovisioning action dialog, select the one of the following action
to deprovision:
1. In the Synchronization Service Console, open the Sync Workflows tab, and then
click the AD to OneIM Sync workflow.
2. Click Add synchronization step.
3. In the Select an action dialog, select Creation, then click Next.
4. In the Specify source and criteria dialog, click Specify, click Add new
connected system or Select existing connected system, then progress through
the wizard to add the Active Directory Test AD as a connected system.
5. In Specify object type field, click Select and from the Select Object type list,
select Group, then click OK.
6. In the Provisioning Criteria section, click Add.
7. In the Select Container dialog, from the containers list, select the required
container and click OK.
8. Click Next.
9. In the Specify target dialog, click Specify.
1. Create a sync workflow for provisioning data synchronization between the source
(Active Directory) and target (One Identity Manager) system.
2. Add a creating step for the workflow to provision users from the source system to
target system.
3. Click on the synchronization step for provision of users.
4. On the General Options tab, specify the delta process mode:
a. Under Source Connected System, select Process delta from last run.
b. Under Target Connected System select Process delta from last run.
5. Click Save and continue.
NOTE: Before any data has been processed from the source to the target
system, the initial synchronization of data is always performed in the Process
all delta mode.
6. Run the configured creating step.
The data for the users added or updated to the source since the previous run, is
displayed under Processed Objects.
1. Mapping objects by configuring one or more mapping pairs and mapping rules.
By mapping objects, you can specify logic checks by which Active Roles
Synchronization Service can identify if two data entries stored in two separate
databases are the same or not.
l With mapping pairs, you can establish a relationship between object types in
two connected systems.
l With mapping rules, you can define the conditions on how the objects specified
in the mapping pair will be mapped during synchronization.
You can use object mapping, for example, to identify the same data entries
between a SuccessFactors HR database (connected to Active Roles via a
Generic SCIM Connector connection) and an SQL server (connected to
Active Roles Synchronization Service via a Microsoft SQL Server
Connector).
To do so, you can set up a mapping that compares the User ID value of the
data entries in the two systems. If the data entries in the two systems share
the same User ID, Active Roles will consider them the same.
For more information on object mapping, see Mapping objects. For an example
mapping procedure using the Generic SCIM Connector, see Creating object
mapping between a SCIM connection and an SQL connection.
The following chapters will provide an example for setting up a sync workflow that will
import data from a SuccessFactors HR database via a Generic SCIM Connector
connection, and synchronizing that data to an SQL database.
The following example procedures show how to create a mapping pair and a mapping
rule between:
l A SuccessFactors HR database connected to Active Roles Synchronization Service
with the Generic SCIM Connector. The SuccessFactors HR database will be the
source system from which Active Roles Synchronization Service imports the data.
l An SQL database connected to Active Roles Synchronization Service with the
Microsoft SQL Server Connector. The SQL database will act as the target
system to which Active Roles Synchronization Service will synchronize the
SuccessFactors HR data.
You can perform the following procedures only if Active Roles Synchronization Service
already contains the following working connectors:
l A Generic SCIM Connector connecting Active Roles Synchronization Service to the
Starling Connect SuccessFactors HR connector. To configure such a connection, see
Configuring the Generic SCIM Connector for Starling Connect connections. In this
example procedure, this connection is called SCIM Connection to
SuccessFactors HR.
l A Microsoft SQL Server Connector providing connection to the SQL Server used in
this example. To configure such a connection, see Creating a Microsoft SQL Server
connection. In this example, this connection is called SQL Connection.
1. In Active Roles Synchronization Service, navigate to Mapping, then click the SCIM
Connection to SuccessFactors HR connection.
2. To start configuring a new object mapping with the Add mapping pair dialog, click
Add mapping pair.
3. In the Specify source step, under Connected system object type, select the
resource object type you want the object mapping to check. In this example, we are
using the Employees data entry of the SuccessFactors HR database, so click Select,
then in the Select Object Type step, select Employees.
TIP: If the data entry is hard to find due to the length of the list, use the Filter by
name field to find it quicker.
To apply your selection, click OK, then Next.
Once the mapping pair is created, you can configure its associated mapping rule.
1. In Active Roles Synchronization Service, navigate to Mapping, then click the SCIM
Connection to SuccessFactors HR connection.
2. The previously configured mapping pair appears. To open the available mapping pair
settings, click the Employees object type in the mapping pair.
3. To start configuring a new mapping rule, in the Mapping pair window, click Add
mapping rule.
4. In the Define Mapping Rule window, specify the source and target resource object
types that must be equal so that Active Roles Synchronization Service can map the
data pairs. In this example, we are using the UserID attribute for this purpose both in
the SuccessFactors HR database and in the SQL database as well.
6. To start the mapping synchronization based on the configured value pair of the
mapping rule, click Map now. Active Roles Synchronization Service offers two
mapping types:
l Quick Map, using local cached data to speed up the mapping process.
l Full Map, retrieving data from the source and target data system for accuracy.
As this is the first time of running this mapping, perform a Full Map.
Once the mapping rule finishes running successfully, it will indicate the unmapped,
changed and mapped objects, along with the objects that do not meet the scope conditions
of the configured mapping rule.
Prerequisites
Before performing the procedure, make sure that the following conditions are met:
l Active Roles Synchronization Service must already contain the following working
connectors:
l A Generic SCIM Connector connecting Active Roles Synchronization Service
to the Starling Connect SuccessFactors HR connector. To configure such a
connection, see Configuring the Generic SCIM Connector for Starling Connect
connections. In this example procedure, this connection is called SCIM
Connection to SuccessFactors HR.
l A Microsoft SQL Server Connector providing connection to the SQL Server
used in this example. To configure such a connection, see Creating a Microsoft
SQL Server connection. In this example, this connection is called SQL
Connection.
l The mapping pair and mapping rule configured in Creating object mapping between a
SCIM connection and an SQL connection are active and working.
1. In Active Roles Synchronization Service, click Sync Workflows > Add sync
workflow.
2. In the Sync workflow name step, name the workflow (for example,
SuccessFactors HR to SQL Server), then click OK.
The new workflow then appears in the Sync Workflows tab.
3. Configure a data synchronization creation step for the workflow. To do so, in Sync
Workflows, click the name of the workflow (in this example, SuccessFactors HR
to SQL Server), then click Add synchronization step.
d. To apply the forward synchronization rule created for the specified user name
attributes, click OK.
e. To configure synchronization rules for the userId, emails.value and
name.familyName SuccessFactors HR data entries too, click Forward Sync
Rule again, and repeat the previous sub-steps by selecting the source and
target attributes applicable to these data entries.
8. Once all forward synchronization rules are configured, to finish configuring the
Creation step, click Finish.
This creates the Creation step as the first step of the sync workflow.
9. Now that the Creation step of the workflow is configured, configure the Update
step. To do so, click Add synchronization step again.
The Update step of the workflow will be used to update existing data entries mapped
between the SuccessFactors HR database and the target SQL database. The Update
step performs data synchronization only for existing data entries: it does not create
new ones. Because of this, you typically run this step after running the Creation
step, and run only the Update step later once the data entries have been created
with the Creation step.
10. In the Select an action step, select Update, then click Next.
11. In the Specify source and criteria step, configure the following settings:
l Source connected system: Specify the SuccessFactors HR database
connection here, created with the Generic SCIM Connector. To do so, click
Specify > Select existing connected system, then select the SCIM-based
connection (in this example, SCIM Connection to SuccessFactors HR).
l Source object type: Specify the source object type here (in this example, the
Employees object type). To do so, click Select, then in the Select Object Type
window, select Employees, and click OK.
TIP: If the data entry is hard to find due to the length of the list, use the
Filter by name field to find it quicker.
l (Optional) Creation Criteria: Specify additional conditions that the specified
source object(s) must meet for synchronization in this workflow step. This
setting is not used in this example.
12. In the Specify target step, configure the following settings:
l Target connected system: Specify the SQL Server connection here, created
with the Microsoft SQL Server Connector. To do so, click Specify > Select
existing connected system, then select the SQL Server connection (in this
example, SQL Connection).
l Target object type: Specify the target object type here. By default, when
selecting an SQL Server connection in Target connected system, Active
Roles Synchronization Service sets this setting to sql-Object, the object type
used in this example.
16. Once Active Roles Synchronization Service found all mapped objects, apply the
synchronization changes by clicking Commit.
Alternatively, to check detailed information about the processed objects, click the
Processed objects number. The Objects processed in window then opens, listing
all new data objects that Active Roles Synchronization Service will synchronize to the
target SQL database.
"name": {
"givenName": "Sam",
"familyName": "Smith",
"formatted": "Sam Smith"
},
The value of complex single-value attributes is the sum of the sub-attribute values.
l Complex multi-value attributes, that is, data entries with multiple complex
values, each of them specified with several simple sub-attributes. For example, the
following addresses attribute is a complex multi-value attribute, specifying several
addresses, each of them being a complex value containing several simple sub-
attributes:
However, even though sync workflows using connections set with the Generic SCIM
Connector can import all three of these value types, Active Roles Synchronization Service
does not recognize complex single-value attributes and complex multi-value attributes, as
they contain more values than what Active Roles Synchronization Service can identify for a
single data entry by default.
To import complex single-value and multi-value attributes successfully, you can use the
following methods:
l For complex single-value attributes, you can map each individual sub-attribute
of the complex single-value attribute to separate attributes in the target system. For
example, in case of the name complex single-value attribute, you can map the
givenName, familyName and formatted sub-attributes to separate name.givenName,
name.familyName, and name.formatted attributes in the target system, respectively.
l For complex multi-value attributes, you can use two methods:
l When importing complex multi-value attributes, Active Roles Synchronization
Service can take a single value (and its sub-attributes), map the sub-attributes
to a set of target values (similarly to complex single-value attributes), then
discard the rest of the complex values of the attribute.
By default, Active Roles Synchronization Service takes the primary value of
the complex multi-value attribute (marked with a specific primary sub-
attribute). If no primary value is specified within the complex multi-value
attribute, Active Roles Synchronization Service imports the first value (and its
sub-attributes) only.
NOTE: This method imports only the primary value (or the first value, if no
primary value is specified). Active Roles Synchronization Service will discard
all other values (and their sub-attributes).
l If you map a complex multi-value attribute (such as the addresses attribute
shown in the above example) when configuring a mapping rule for a workflow,
1. In the Active Roles Synchronization Service, click Sync Workflow, then click the
sync workflow that imports data from a SCIM-based source system (for example, the
SuccessFactors HR to SQL Server workflow used in Creating a sync workflow for
synchronizing data from a SCIM-based Starling Connect connector).
2. Click the first step of the workflow (in the example SuccessFactors HR to SQL
Server workflow, this is named Step 1 (Creation from SCIM Connection to
SuccessFactors HR to SQL Connection).
3. Under Creation Rules, to open the initial population rules, click Forward
Sync Rule.
4. In the Forward Sync Rule window, at the Source item setting, open the Attribute
drop-down, and click PowerShell Script.
5. In the PowerShell Script Editor, paste the following script example, and click OK:
if ($addressesJsonArray) {
for ($i = 0; $i -lt $addressesJsonArray.Length; $i++) {
if ($addressesJsonArray[$i].type -eq "work") {
return $addressesJsonArray[$i].streetAddress + ", " +
$addressesJsonArray[$i].region + ", " + $addressesJsonArray[$i].locality
}
}
}
You can configure synchronization rules for such steps as creating, deprovisioning, or
update. Synchronization Service provides a user interface (Synchronization Service
Console) that allows you to set up a direct or rules-based synchronization rule
without any coding.
However, to set up a script-based synchronization rule, you must develop a Windows
PowerShell script that will build values of the target object attributes using values of the
source object attributes.
This section provides some reference materials on using the Windows PowerShell Script
Host feature and provides the sample script.
#Returns "JDoe@mail1.mycompany.com
$strSourceMail=$srcObj["mail"]
#Returns JDoe@mail2009.mycompany.com
$strTargetMail=$DstObj["mail"]
#Returns JDoe@mail1.mycompany.com (5 January, 2010)
$strNewMail=$Request["mail"]
Example script
# --- Retrieve the City attribute of the user object in connected data
source.
$userCity = $srcObj["City"]
# --- Determine the user's country
switch ($UserCity)
{
"New York" {$country = "United States"; break}
"Paris" {$country = "France"; break}
"Tokyo" {$country = "Japan"; break}
default {$country = "Unknown"}
}
# --- Return the user country. The script-based creating rule
# --- assigns this value to the "co" attribute in the created user object.
$country
# End of the script
You can use a Windows PowerShell script in a password sync rule to transform passwords.
This section provides some reference materials on how to write a Windows PowerShell
script for password transformation.
Example script
To clarify the use of $srcPwd, consider a scenario where the target object password in
the target connected data system must include only 8 first characters of the source
object password in the source Active Directory domain.
The following scripts implements the described scenario:
About us
One Identity solutions eliminate the complexities and time-consuming processes often
required to govern identities, manage privileged accounts and control access. Our solutions
enhance business agility while addressing your IAM challenges with on-premises, cloud and
hybrid environments.
For sales and other inquiries, such as licensing, support, and renewals, visit
https://www.oneidentity.com/company/contact-us.aspx.
Technical support is available to One Identity customers with a valid maintenance contract
and customers who have trial versions. You can access the Support Portal at
https://support.oneidentity.com/.
The Support Portal provides self-help tools you can use to solve problems quickly and
independently, 24 hours a day, 365 days a year. The Support Portal enables you to:
l Submit and manage a Service Request
l View Knowledge Base articles
l Sign up for product notifications
l Download software and technical documentation
l View how-to videos at www.YouTube.com/OneIdentity
l Engage in community discussions
l Chat with support engineers online
l View services to assist you with your product