Subscribe to Help Center RSS FeedPostponed: JumpCloud will upgrade the hashing function used when syncing passwords to Google to the most secure hashing function they support for password synchronization.
Google requires that all passwords synced via API be hashed, which they in turn re-hash according to their password security policies. This enhancement ensures your directory sync meets modern encryption standards and resolves a known issue where the older format triggered security warnings within Google.
Note: If you have any questions or concerns about this change, please contact your Customer Success Manager or Account Manager.
What’s Changing?
The hashing function used to hash passwords when syncing them to Google will be upgraded. The original upgrade approach would have been disruptive to end-users, ending their Google Workspace sessions and requiring them to re-login across their browser sessions, devices, and Chrome profiles. A new approach was developed which has no end-user impact.
- Seamless Transition: The security update will only be applied when a user naturally changes their password.
- Zero Disruption: This new strategy ensures your users will not be logged out of their active Google sessions unexpectedly.
- No Action Required: No action is required from you or your end-users.
In this Article