Warning:<\/strong> \nUsers 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\n- When the JumpCloud AD import agent is installed on all DCs<\/strong>, the AD password does<\/strong> sync from AD to JumpCloud. This means that the password will be saved in both AD and JumpCloud. \n
\n- When a user’s Password Authority<\/strong> is set to None (JumpCloud)<\/strong><\/strong>:\n
\n- Passwords can be managed in AD, JumpCloud, or both.<\/li>\n\n\n\n
- Password expiration notifications are sent from JumpCloud.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- When a user’s Password Authority<\/strong> is set to Active Directory<\/strong><\/strong>:\n
\n- The password cannot be set or changed password in JumpCloud, with the exception of the link from the password expiration notification.<\/li>\n\n\n\n
- Passwords must be managed in AD.<\/li>\n\n\n\n
- Password expiration notifications are sent from JumpCloud.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
User Sync Considerations<\/h3>\n\n\n\n\n- Synced users must have values for <First Name> and <Last Name>, i.e., the first name and last name fields cannot be empty, otherwise the users will fail to sync.<\/li>\n\n\n\n
- The JumpCloud ADI import and sync agent services use TLS for all communication. If no network connectivity exists to JumpCloud, the ADI won\u2019t work properly <\/li>\n<\/ul>\n\n\n\n
Sync from AD to JumpCloud<\/strong><\/p>\n\n\n\n\n- We recommend that all users you plan to import from AD into JumpCloud live in a single OU or be nested underneath a chosen OU (Root user container) in AD. This can be the default CN=Users container in AD or an alternate custom OU in the directory.\n
\n- If you relocate users in AD outside of the Root User Container, you could disrupt password synchronization, or remove users and groups from your JumpCloud instance, along with any associated data and resource associations.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- To sync users from AD to JumpCloud, users must be members of the ADI specific Security Group (e.g., \u201cJumpCloud\u201d or “JumpCloud -Domain1”) or of a Security Group nested under this Security Group<\/li>\n\n\n\n
- Users who are imported from AD to JumpCloud will automatically have their Password Authority<\/strong> set to Active Directory<\/strong> by default and the attributes that sync will be read-only in both the Admin Portal and in User Portal. These fields become restrictedFields.<\/li>\n\n\n\n
- You can manage users in 2 ways:\n
\n- Individually by adding them to the security group created for this integration, located in the designated OU <\/li>\n\n\n\n
- Using groups located in or nested in the designated Root user container by adding those groups as a member of the JumpCloud Integration Security Group<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- ADI Import Agent settings in the jcadimportagent.config.json<\/strong> file control the behaviors that occur in JumpCloud when certain actions are taken on the user in AD\n