As of March 31, customers within the US can now replace their Google Account username whereas maintaining their account, inbox, and information totally intact. In case your platform makes use of Check in with Google or identifies customers by e-mail, this put up explains how this replace impacts your integration and any steps you might must take.<\/p>\n

Many customers have outdated e-mail addresses that not replicate who they’re\u2014whether or not as a result of a reputation change, a shift in skilled id, or just a username that they’ve outgrown.<\/p>\n

With this replace, when a person adjustments their username, their authentic e-mail deal with is retained as a substitute linked to the identical account. Each emails level to the identical inbox. Customers can proceed to register, ship, and obtain e-mail utilizing both. Whereas this functionality has been out there to enterprise Workspace customers<\/a>, we’re now increasing it to client Google Accounts with a @gmail.com deal with.<\/p>\n<\/div>\n

What it means to your platform<\/b><\/h3>\n
How this function impacts your customers is dependent upon how they authenticate together with your platform and the way your platform identifies them.<\/p>\n
Check in with Google customers, recognized by topic ID<\/b><\/p>\n
In case your platform already makes use of topic ID<\/a> as the first account identifier, no motion is required. The topic ID is secure and won’t change, no matter any adjustments made to the e-mail deal with.<\/p>\n
Check in with Google customers, recognized by e-mail deal with<\/b><\/p>\n
In case your platform makes use of Check in with Google, and maps person accounts primarily based off of the e-mail deal with from the ID token, some customers might expertise disruption after altering their username.<\/p>\n
\n
If an OAuth grant from earlier than the username change stays lively<\/b>, Google will proceed to supply the outdated e-mail deal with to take care of continuity. The person authentication expertise ought to sometimes stay uninterrupted.<\/li>\n<\/ul>\n
\n
Nonetheless, if an OAuth grant was revoked by the person,<\/b> Google will present the brand new e-mail deal with as an alternative on subsequent register. This may increasingly trigger your platform to fail to acknowledge the person, doubtlessly leading to duplicate accounts and lack of entry to current information.<\/li>\n<\/ul>\n
As a greatest apply, we suggest migrating to topic ID as your main person identifier<\/a>. See the suggestions part under.<\/p>\n
Handbook account and password customers<\/b><\/p>\n
For customers who register with e-mail and password, the sign-in expertise can be unaffected. The person\u2019s outdated e-mail deal with stays lively, to allow them to proceed signing in as regular. Since a person initially created the account in your platform utilizing an e-mail deal with and password, your platform has no topic ID on file; it solely is aware of the e-mail deal with.<\/p>\n
\n
Danger of duplication:<\/b> If the person later makes an attempt to make use of Check in with Google with a brand new e-mail deal with, your platform can be unable to hyperlink this new Google id to an current account, which may create a replica account.<\/li>\n<\/ul>\n
To forestall this from occurring, enable customers to replace the e-mail deal with related to their account in your platform. This permits customers to seamlessly register to their current account utilizing Check in with Google, alongside e-mail and password.<\/p>\n
A notice on passkeys<\/b><\/p>\n
For customers who use passkeys to signal into your platform, this function won’t impression their sign-in expertise.<\/p>\n
Our Suggestions<\/b><\/h3>\n
To make sure a clean transition to your customers, we suggest following these three steps:<\/p>\n
\n
Use topic ID as your main person identifier.<\/b> Topic ID (sub) is probably the most dependable identifier for a Google person and stays unchanged even when a person updates their e-mail deal with. We strongly suggest utilizing it as the first key for any person account authenticated through Check in with Google. You’ll find extra technical particulars on Topic ID<\/b> in our implementation greatest practices<\/a>.<\/li>\n<\/ul>\n
\n
Present email-based account restoration.<\/b> If adopting the topic ID shouldn’t be instantly possible, providing email-based account restoration is crucial. Since Google retains the outdated e-mail deal with as an alias, restoration messages despatched to the unique deal with will nonetheless attain the person.<\/li>\n<\/ul>\n
\n
Allow e-mail updates.<\/b> For customers who signed as much as your platform with conventional e-mail and password accounts, enable them to replace their contact data inside your platform settings to forestall sign-in points.<\/li>\n<\/ul>\n
We encourage you to assessment your present authentication choices and implement these updates to take care of a seamless person expertise.<\/p>\n
An incredible expertise to your customers<\/b><\/h3>\nWith these enhancements, we\u2019re making customers\u2019 expertise less complicated and safer, so customers can simply keep engaged in your platform. You probably have any questions, go to builders.google.com<\/a>.<\/p>\n<\/div>\n\n","protected":false},"excerpt":{"rendered":"
As of March 31, customers within the US can now replace their Google Account username whereas maintaining their account, inbox, and information totally intact. In case your platform makes use of Check in with Google or identifies customers by e-mail, this put up explains how this replace impacts your integration and any steps you might […]<\/p>\n","protected":false},"author":2,"featured_media":13677,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[56],"tags":[1323,205,1136,81,3788,8463],"class_list":["post-13675","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-software","tag-account","tag-app","tag-change","tag-google","tag-supporting","tag-username"],"_links":{"self":[{"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=\/wp\/v2\/posts\/13675","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=13675"}],"version-history":[{"count":1,"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=\/wp\/v2\/posts\/13675\/revisions"}],"predecessor-version":[{"id":13676,"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=\/wp\/v2\/posts\/13675\/revisions\/13676"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=\/wp\/v2\/media\/13677"}],"wp:attachment":[{"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=13675"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=13675"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/techtrendfeed.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=13675"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}