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.
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.
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:
Microsoft Active Directory Domain Services
Microsoft Active Directory Lightweight Directory Services
Microsoft Exchange Server
Microsoft Skype for Business Server
Microsoft Azure Active Directory
Microsoft 365
Microsoft SQL Server
Microsoft SharePoint
Active Roles version 7.4.x, 7.3, 7.2, 7.1, 7.0, or 6.9
One Identity Manager version 8.1, 8.0, or 7.0
Data sources accessible through an OLE DB provider
Delimited text files
Generic LDAP Directory service
MYSQL Database
OpenLDAP Directory service
Salesforce
ServiceNow
IBM DB2 Database
IBM RACF Connector
IBM AS/400 Connector
Oracle Database connector
Oracle Database User Accounts connector
Micro Focus NetIQ Directory connector
Oracle Unified Directory connector
In any hybrid environment, on-premises Active Directory objects are synchronized to Azure AD using some means such as Azure AD Connect. When Active Roles is deployed in such a hybrid environment, the existing users and groups' information, such as Azure objectID, must be synchronized back from Azure AD to on-premises AD to continue using the functionality. To synchronize existing AD users and groups from Azure AD to Active Roles, we must use the back synchronization operation.
Back synchronization is performed by leveraging the existing functionality of Active Roles Synchronization Service. Sync workflows are configured to identify the Azure AD unique users or groups and map them to the on-premises AD users or groups. After the back synchronization operation is completed, Active Roles displays the configured Azure attributes for the synchronized objects.
The Azure BackSync Configuration feature allows you to configure the back synchronization operation in Azure with on-premises Active Directory objects through the Synchronization Service Web Interface. The required connections, mappings, and sync workflow steps are created automatically.
When you configure the back synchronization, the Azure App registration is done automatically with the default app ActiveRoles_AutocreatedAzureBackSyncApp_V2.
NOTE: Consider the following when configuring Azure BackSync:
In case of an Application not found error, please try the configure back synchronization operation again after some time, since the Azure App synchronization may take some time.
If you use the existing back synchronization configuration settings, then the existing default app ActiveRoles_AutocreatedAzureBackSyncApp is used to run the back synchronization workflow. However, it is recommended to use the default app ActiveRoles_AutocreatedAzureBackSyncApp_V2 since it requires reduced administrator privileges. To use the latest Azure App, configure the back synchronization again. For information on how configure the back synchronization, see Configuring Azure BackSync.
For the back synchronization to work as expected, the user must have write permissions for edsvaAzureOffice365Enabled, edsaAzureContactObjectId, edsvaAzureObjectID, and edsvaAzureAssociatedTenantId. The user must also have a local administrator privileges where the Active Roles Synchronization Service is running.
The following illustration shows how Synchronization Service synchronizes data between connected data systems.
Figure 1: Synchronization of data between connected systems
Synchronization Service uses Capture Agents, connected data systems, connectors, connections, and sync workflows to synchronize identity data.
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center