If you experience an issue when performing an Active Directory Integration (ADI) with JumpCloud, review these common resolutions.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Here is an excellent reference for common LDAP Result Code error meanings.
https:\/\/ldap.com\/ldap-result-code-reference\/<\/a><\/p>\n<\/div><\/div><\/div>\n\n\n\n
<\/p>\n\n\n\n
<\/p><\/div>
The password listed in the adint.config.json <\/strong>will likely be a secure hash, enter the new password between quotes.<\/p>\n\n\n\n
After the service has started, the password will be re-hashed in the .json file.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
<\/p><\/div>
The separator for DN is a semicolon and not a comma. For example, CN=Users;DC=contoso;DC=com.<\/p>\n <\/div><\/div><\/div><\/div>\n<\/div><\/div><\/div>\n\n\n\n
<\/p>\n\n\n\n
<\/p><\/div>
<\/p>\n\n\n\n
As in the previous step, if the API key associated with a JumpCloud administrator used to set up AD Import is rotated, or the admin is deleted, the import service will stop working. This means password changes and new user imports will no longer work as expected. <\/p>\n\n\n\n
See Rotate the AD Import API Key<\/a> for steps on how to update the API key in the AD Import configuration.<\/p>\n<\/div><\/div><\/div>\n\n\n\n
RESOLUTION 1:<\/strong><\/p>\n\n\n\n
<\/p><\/div>
Starting the service will update the bind_pw_encrypted hash and remove the bind_password key.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
RESOLUTION 2: <\/strong>Error:agent no longer registered, Please uninstall and re-install with a valid connect key<\/strong><\/p>\n\n\n\n
<\/p>\n\n\n\n
<\/p><\/div>
If users were created after the AD Import Agent\u2019s install, then no password change is required by that AD User. The password is immediately exported to JumpCloud. <\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
<\/p>\n\n\n\n
<\/p><\/div>
Ensure the use of semicolons to separate the DN fields. Using commas will result in the application failing to sync.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
<\/p>\n\n\n\n
See the article Convert AD-managed User Accounts<\/a>.<\/p>\n<\/div><\/div><\/div>\n\n\n\n
This can be due to the default service timeout being too short.<\/p>\n\n\n\n
<\/p>\n\n\n\n
If you are using JumpCloud with your Active Directory server, leveraging the JumpCloud ADI, you may find that sudo\/administrator permissions are periodically lost after you set them within JumpCloud. The AD Import agent controls user attributes and membership in JumpCloud via AD security groups, and this is the case for the sudo\/admin user setting.<\/p>\n\n\n\n
When using the JumpCloud AD Import agent, there are two AD security groups that you use to control behavior in JumpCloud. Both need to be created in the Users OU.<\/p>\n\n\n\n