{"id":97084,"date":"2023-10-26T20:42:21","date_gmt":"2023-10-27T00:42:21","guid":{"rendered":"https:\/\/jumpcloud.com\/?post_type=support&p=97084"},"modified":"2024-08-20T13:23:38","modified_gmt":"2024-08-20T17:23:38","slug":"configure-adi-two-way-sync","status":"publish","type":"support","link":"https:\/\/ti-1.jumpcloud.com\/support\/configure-adi-two-way-sync","title":{"rendered":"Configure ADI: Manage users, groups and passwords in AD, JumpCloud, or both"},"content":{"rendered":"\n
The JumpCloud Active Directory Integration (ADI) enables the syncing of users, groups, and passwords between JumpCloud and on-premise or off-premise AD. As covered in Get Started: Active Directory Integration<\/a>, the ADI uses two agents: an Import Agent and a Sync Agent that can be installed in three (3) configurations which are based on where you want to manage users, groups, and passwords:<\/p>\n\n\n\n This article provides a step-by-step guide for configuring ADI to manage users, security groups, and passwords in AD, JumpCloud, or both<\/strong>. This configuration provides the greatest flexibility. It allows AD and JumpCloud to manage user credentials and attributes together in unison, a full two-way sync. Users are able to change passwords within either AD or JumpCloud. It also supports a hybrid approach where specific information is managed in one system and other information is managed in the other system. This configuration supports:<\/p>\n\n\n\n To sync passwords from AD to JumpCloud, the import agent must be installed on all<\/strong><\/em> DCs.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n To explore the use cases and benefits of this configuration see Manage users and passwords in either system, or both<\/a> in the Configure Active Directory Integration (ADI)<\/a> help center article.<\/p>\n\n\n\n To learn more about the general user identity workflow and expected behavior for any user, group, and password change after the AD Import and AD Sync agents have been configured, read Use and Manage the Active Directory Integration (ADI)<\/a> . <\/p>\n\n\n\n The main steps you will take to install and configure AD for bi-directional use are:<\/p>\n\n\n\n Import Agent<\/strong><\/p>\n\n\n\n When upgrading from AD import agent v2.6.0 or lower, you must select Install New Agent<\/strong> from the Downloads dropdown menu in the ADI Details page to get the connect key, which is required to complete the upgrade of the agent on the AD server.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n Sync Agent<\/strong><\/p>\n\n\n\n The delegated authentication functionality is specific to the ADI AD import agent. Review ADI: Use AD Delegated Authentication<\/a> for specific considerations and more information about delegated authentication to AD. <\/p>\n\n\n\n When the delegated authentication setting, Delegated Password Validation<\/strong>, is enabled and Pending<\/strong> for the ADI configuration and the user’s Delegated Authority<\/strong> is Active Directory<\/strong>, the user will not be able to log in. An AD import agent, version 3.0 or higher, must be installed and active to change the status of Delegated Password Validation<\/strong> from Pending<\/strong> to Active<\/strong>. <\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n When upgrading the AD import agent to version 3.0, existing users connected to the domain will not have their log in delegated to AD unless the Delegated Authority<\/strong> is manually set to Active Directory<\/strong> for those existing users.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n All installed agents should be the same version to avoid unexpected behavior or the potential for users not being able to log in if the primary agent is switched.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n You must reboot the servers after the AD Import Agent installation.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n You DO NOT need to reboot the servers after the AD Sync Agent installation.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n In multi-domain environments, the security group must have a unique name within each domain (e.g., \u201cJumpCloud (mydomain1)\u201d and \u201cJumpCloud (mydomain2)\u201d)<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n The following are considerations only if you choose to install the ADI agents on member servers:<\/p>\n\n\n\n Import Agent<\/strong><\/p>\n\n\n\n Sync Agent<\/strong><\/p>\n\n\n\n The following are considerations only if you choose to install the agents on DCs:<\/p>\n\n\n\n Import Agent<\/strong><\/p>\n\n\n\n Sync Agent<\/strong><\/p>\n\n\n\n If the JumpCloud Administrator Account associated with the import is deleted or the API key is rotated, the import will stop working. All imports will fail until a valid API key is generated and updated in the registry on the AD servers.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n Users will not be able to log in to JumpCloud User Portal or SSO apps if JumpCloud AD import agent is installed on member servers<\/strong>, the user’s Password Authority<\/strong> is set to Active Directory<\/strong>, and the user’s Delegated Authority<\/strong> is set to None<\/strong>. <\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n Sync from AD to JumpCloud<\/strong><\/p>\n\n\n\n Export and sync from JumpCloud to AD<\/strong><\/p>\n\n\n\n Regular<\/strong><\/p>\n\n\n\n\n
\n
Deployment Configuration Overview<\/h2>\n\n\n\n
\n
<\/p><\/div>
\n
Workflows<\/h2>\n\n\n\n
Two-way sync – single domain<\/h3>\n\n\n\n
<\/figure>\n\n\n\n
Two-way sync – multiple domains<\/h3>\n\n\n\n
<\/figure>\n\n\n\n
System Requirements<\/h2>\n\n\n\n
\n
\n
Installation Steps Overview<\/h2>\n\n\n\n
\n
Considerations<\/h2>\n\n\n\n
Agent Version Considerations<\/h3>\n\n\n\n
<\/p><\/div>
\n
\n
\n
\n
Delegated Authentication Considerations<\/h3>\n\n\n\n
<\/p><\/div>
<\/p><\/div>
\n
\n
\n
General Installation Considerations<\/h3>\n\n\n\n
<\/p><\/div>
<\/p><\/div>
<\/p><\/div>
\n
\n
<\/p><\/div>
\n
\n
Member Server Installation Considerations<\/h3>\n\n\n\n
\n
\n
Domain Controller (DC) Installation Considerations<\/h3>\n\n\n\n
\n
\n
Security Considerations<\/h3>\n\n\n\n
\n
<\/p><\/div>
Password Considerations<\/h3>\n\n\n\n
\n
\n
\n
\n
<\/p><\/div>
\n
\n
\n
\n
User Sync Considerations<\/h3>\n\n\n\n
\n
\n
\n
\n
\n
\n
Migrating device accounts from AD Managed to JumpCloud Managed<\/h3>\n\n\n\n
\n