Use these release notes to review improvements and new features in each version of Password Sync.
Release notes for 1.8.17
April 6, 2022
What's new- Best security practices implemented to help keep your users' accounts and data safe.
Release notes for 1.8.13
June 24, 2021
What's new- G Suite Password Sync (GSPS) is now Password Sync.
- Improved the application logo and icons.
- Minor UI changes to the Welcome screen.
- Installer's command-line interface no longer requires the DOMAIN argument.
- Password Sync now logs the cause of any "access denied" errors that happen while trying to save the admin credentials.
- Updated URL in the error message that's logged when a password contains invalid characters.
- Improved error message when the configuration XML file can't be found.
Release notes for 1.7.6
September 16, 2019
What's new- GSPS now works when additional LSA protection is enabled on a Windows Server.
- Entering the domain name is no longer required.
- Information for better diagnostics (admin email address and service account ID) has been added to the log file.
- Fixed the error message help text that's shown when using anonymous access on a system where anonymous access isn't supported.
- Fixed an issue that caused LDAP searches to fail to log a username that is isn't correct (usually garbage data instead of the actual username).
- Minor logging fixes.
Release notes for 1.6.17
January 30, 2017
What's fixedRelease notes for 1.6.13
November 8, 2016
What's newRelease notes for 1.6
June 30, 2016
What's new- Added support for Windows Server Core 2008 and 2012 installations.
- Added Service Account support for G Suite authentication. This is required for Server Core installations and is optional on non Server Core installations.
- GAPS can now be installed and configured from the command line.
- LDAP configuration can now use the GAPS service security context, removing the need to provide Active Directory administrator credentials.
- Improved error messages in the configuration wizard.
- Added crash reporting. The reports are stored on the GAPS server and not transmitted to Google.
- Windows Server 2003 is no longer supported.
- The GAPS UI now correctly displays an egg timer icon while performing tasks triggered by other actions, such as the user pressing the Previous, Next, and Authorize Now buttons.
- GAPS will retry network timeouts and 5xx server errors encountered when trying to refresh its OAuth access token.
- Users who are not Windows domain admins can no longer start the GAPS configuration wizard. Previously, they could open the wizard but receive an error when trying to save the configuration.
Release notes for 1.5
February 16, 2016
What's newGAPS now uses the Crypt hash function (salted SHA512 hashes instead of SHA1) when updating the password with the Directory API.
Uses new OAuth2 endpoints to authorize and refresh tokens (avoids conflict when overriding DNS to enforce SafeSearch).
Improved feedback in the configuration UI to help diagnose issues with authorization. Improved trace logging and Windows Event Log system messages.
The number of log events has been reduced when a computer account password fails to sync.
Improved diagnostic logging for authorization issues can now be found in the service authorization logs.
Note: There is a new version of the GAPS support tool available to help you troubleshoot your GAPS installation.
Release notes for 1.4
What's fixedFixed an issue where, after failing to retrieve the email address attribute for an account from Active Directory, GAPS silently crashes.
Note: This issue has only been observed on Windows Server 2003, but we recommend upgrading regardless of your Windows Server version.
Release notes for 1.3
What's newGAPS now uses the Admin SDK - Directory API (version 1).
The "Configure G Suite" and "Configure Active Directory" pages now perform validation. If you enter incorrect information in any of them, the program will alert you.
The log files generated by GAPS no longer show irrelevant log lines mentioning Outlook.
In the "Configure G Suite" wizard page, pressing Enter will now prompt you to authorize instead of taking you back to the previous page.
Release notes for 1.2
What's new"G Suite Passwords" events now appear in the Application event log. GAPS now logs password sync success and failures details to the event log.
Fixed an issue where the steps listed in the initial configuration wizard page were in the wrong order.
Fixed an issue where GAPS was logging the password hashes in some cases if the password failed to sync. GAPS no longer logs the password hashes.
Fixed an issue that made GAPS try to sync passwords that contained unsupported characters (non US-ASCII characters). Now GAPS logs a warning.
GAPS now correctly identifies password sync failures when a server error response is returned.
Formatting issues with the GAPS DLL logs have been fixed.
Release notes for 1.1
What's new"Use Anonymous access to query Active Directory" is now unchecked by default. Most Active Directory environments don't allow anonymous LDAP connections, so this simplifies the setup process.
GAPS 32-bit will no longer install on 64-bit systems. Previously, the installation completed without error, but password sync wouldn't work. Now, the two installers can no longer be confused.
Better Google authorization flow. The new authorization flow is clearer and simpler to use.
Automatically detect base DN. When running the configuration wizard for the first time, the base DN field will be pre-filled with your domain's default base DN.
Fixed an issue where the logs incorrectly show "Error while securing the key: 0" even when there's no error saving the settings.
Fixed several issues with the Google authorization step of the configuration that caused it to fail without explanation.
Fixed an issue that made the GAPS service fail to start on some systems because its path was registered in the system without double quotes.
Fixed an issue that caused GAPS to fail when there were incorrect proxy settings on the network.
Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.
