Items Being Released:
- AD Bridge has been released to enable customers who are required to/prefer to continue to leverage Active Directory® as their authoritative directory to gain efficiency binding AD to various cloud-based and other non-MSFT resources. Our AD Bridge simplifies the process of connecting these external resources to AD, ensuring AD maintains its authority as the central directory.
AD Bridge Bug Fixes/Updates
- Now supports Windows Server 2016 (along with 2008 & 2012).
- AD Groups with no users do not get synced to JumpCloud Tags.
- Nested AD groups do not get synced to JumpCloud correctly. Users from such groups will now be flattened in JumpCloud. Example: create a “Parent” group in AD and 2 children groups (“Child1″ and “Child2″) which are members of Parent. All 3 groups will now be created in JumpCloud and the Parent group will contain all users from both Child1 and Child2.
- New users created in AD would sometimes have their password not sync properly to JumpCloud and would appear “unactivated” in JumpCloud.
- Password update on Domain Controller not updated Agent Store Password.
- Syncs would be initiated even when no changes were being made in AD.
- The AD Bridge will now automatically detect password changes made for the AD read-only account (used by the AD bridge to access AD) and update its config file and settings accordingly.
- Optimized AD Queries with a more efficient implementation of AD groups tree traversal.
- AD Bridge fails to add a user if the AD domain name was entered using mixed case while configuring the AD Bridge.
- AD Bridge compares DNs in a case-sensitive manner, causing conflict on update.
- AD Bridge crashes or goes into an infinite loop if you add an AD group as a member of itself. This fix will also apply to recursive loops within nested groups (for instance consider the following group tree with a loop: A -> B -> C -> A).