Apps Documentation & Support
Last updated: March 2013
These release notes describe additions and improvements to the most recent versions of Google Apps Directory Sync (GADS). You can find detailed information in the Google Apps Directory Sync Administration Guide.
Release 3.1.6
What's NewSupport for structured names for Shared Contacts. You can use a combination of LDAP attributes to specify the full name of a shared contact. For example:
[prefix] - [givenName] [sn] [suffix]
Security enhancements. GADS configuration files are now tied to the system they were created on, for enhanced security. If you copy a configuration XML file to another system, you need to re-enter sensitive data, such as passwords and authorizations.
Performance improvements.
Miscellaneous bug fixes.
Improved error messages when a search rule references an LDAP entity that doesn't exist.
Support for LDAP servers that split group member results across multiple entities.
The Configuration Manager now supports displays with lower resolutions.
If a dynamic group search filter causes an error, the rest of the items sync correctly and the erroneous item is reported in the summary, instead of failing the entire sync.
Commas in Canonical Names of dynamic groups' members no longer cause the sync to fail.
GADS now correctly syncs group members who are suspended in Google Apps.
Release 3.1.3
What's NewEmail address rename detection. GADS can detect email address renames on your LDAP server and sync those renames to Google Apps. To use this feature, you need to specify a Unique Identifier Attribute under User Accounts > User Attributes in Configuration Manager. This attribute must have a unique value for each of your users, and the value must not change. The objectGUID attribute is a valid example for Active Directory systems.
GADS version check. GADS checks your current configuration to see whether a previous version of GADS was used to create it. If so, you must verify and save the configuration before using it.
Dynamic groups support. GADS supports dynamic (query-based) groups, where group membership is specified as a query. See Group Search Rules for more information.
64-bit support. A 64-bit version of GADS is now available. Users with compatible systems can use the 64-bit version to improve performance during large syncs.
OAuth 2.0. GADS now uses OAuth 2.0. Existing users of OAuth need to re-authenticate GADS to take advantage of OAuth 2.0.
Syncing groups no longer requires user search rules for newer configurations.
Active Directory users can now quickly configure GADS by generating default values for most attributes and search rules with a single click.
Miscellaneous bug fixes.
Release 3.0.6
What's NewNew look. GADS 3.0.6 has a cleaner, more intuitive user interface.
Configurable password length. Passwords generated by GADS now have a configurable length.
Miscellaneous bug fixes.
Release 2.1.6
What's NewMiscellaneous bug fixes.
Release 2.1.5
What's NewAdded the ability to synchronize only passwords that have changed since the previous sync.
Added the option to prevent a sync from suspending/deleting admin accounts not found in the LDAP server.
Improved performance of the sync simulation UI.
Added support for Base64-encoded passwords.
Logs are now encoded in UTF-8 by default to support non-ISO characters.
The logging level menu now displays options in decreasing order of verbosity.
Added logging for suspended accounts that are not deleted because of the current configuration.
Miscellaneous bug fixes.
Release 2.1.3
What's NewGoogle Apps Directory Sync 2.1.3 includes updates to improve stability and performance, but no new features. Following is a brief description of the issue resolved in this release.
"Invalid request URI" when updating an orgunit
Issue: When attempting to update an orgunit, Directory Sync sometimes failed with an error "Invalid request URI.".
Resolution: Updating orgunits now runs correctly.
New Admin Guide Update
The Google Apps Directory Sync Administration Guide has been updated with extended information on deployment. To view the new guide, see the Google Apps Directory Sync Administration Guide.
Release 2.1.1
Google Apps Directory Sync 2.1.1 includes multiple new features and fixed issues.
Following is a list of issues resolved in this release. Each issue includes the release number, a tracking number, and a brief description.
Performance Improvements
Release 2.1.1 includes substantial performance improvements, including parallel threads and faster retrieval of data. With the new release of Google Apps Directory Sync, you will experience faster performance of synchronizations.
Domain Replacement for User Profiles
In Release 2.1.1, the "Replace domain names in LDAP email addresses (of users and groups) with this domain name" setting will also affect User Profiles. To configure this setting, go to Google Apps Settings in Configuration Manager.
Multiple LDAP attributes support for Given Name and Family Name
In Release 2.1.1, you can specify multiple attributes for a given name or family name in LDAP Extended Attributes. Mark each LDAP attribute with square brackets. Set your LDAP Extended Attributes in Configuration Manager.
Suspend User Limit Provision
Google Apps Directory Sync includes the ability to limit the number of users that are deleted during synchronization. In Release 2.1.1, you can also set a similar limit for the number of users that are suspended during synchronization. Set this limit in the Sync Limits page of Configuration Manager.
Flush Cache During Simulated Synchronization
During simulated synchronization in Configuration Manager, you can clear out all remote cached data so that fresh data is pulled from Google Apps during the next simulation.
Fixed Issues
Release Notes now in new location
Instead of linking to a PDF file, Google Apps Directory Sync release notes are now published in the Help Center.
Misleading error message for Non-Unique Resource ID
Issue: When a Calendar Resource attribute is not unique, the error message does not give a clear description of the reason for failure.
Resolution: The error message for a non-unique Resource ID now shows that more than one resource with the same name were found.
Invalid characters not handled properly for user and group addresses
Issue: Invalid characters are not detected properly during synchronization.
Resolution: Invalid characters are now removed during synchronization.
Misleading message for extra Google Profiles
Issue: The message for extra Google user profiles says that accounts "might have to be deleted" which may be misleading.
Resolution: The warning message now notes that GADS will not sync these additional profiles.
Org-level exclusion rules do not apply if org email addresses have uppercase letters
Issue: Directory Sync will suspend or delete users that have uppercase letters in their email addresses, even if those users are excluded by an org-level exclusion rule.
Resolution: Directory Sync now uses org-level exclusion rules correctly for users with uppercase letters in their email addresses.
Group Display Name information missing from log
Issue: Groups display names were not listed in the synchronization logs.
Resolution: Display names now show correctly in logs.
Release 2.0.3
Google Apps Directory Sync 2.0.3 includes one major fixed issue and no new features.
Following is a list of issues resolved in this release. Each issue includes the release number, a tracking number, and a brief description.
OAuth authentication fails with error "Token Invalid".
Issue: When attempting to synchronize Google Apps Directory Sync while using OAuth for authentication, all synchronization failed with an error "Token Invalid."
Resolution: Synchronization using OAuth authentication now runs properly and does not generate any OAuth errors.
