[NFBCS] G Suite Update: Less secure app turn-off suspended until further notice

Curtis Chong chong.curtis at gmail.com
Tue Mar 31 15:27:22 UTC 2020


Greetings all:

 

I received the following from Google about the timeline for turning off support for "less secure applications". This is significant for users of email clients who need to connect to Gmail but who have not yet updated their email client software.

 

Cordially,

 

Curtis Chong

 

 

From: noreply+feedproxy at google.com <noreply+feedproxy at google.com> 
Sent: Tuesday, March 31, 2020 4:10 AM
To: chong.curtis at gmail.com
Subject: G Suite Update: Less secure app turn-off suspended until further notice

 



 <http://gsuiteupdates.googleblog.com/> G Suite Update: Less secure app turn-off suspended until further notice 

	
  _____  


 <http://feedproxy.google.com/~r/GoogleAppsUpdates/~3/0_2hkD97kQg/less-secure-app-turn-off-suspended.html?utm_source=feedburner&utm_medium=email> Less secure app turn-off suspended until further notice 

Posted: 30 Mar 2020 01:24 PM PDT

Last December, we announced that we’d be  <https://gsuiteupdates.googleblog.com/2019/12/less-secure-apps-oauth-google-username-password-incorrect.html> turning off less secure app (LSA) access to G Suite accounts, and that you should migrate to  <https://developers.google.com/identity/protocols/OAuth2> OAuth authentication instead. The first phase of the LSA turn-down was scheduled for June 15, 2020. As many organizations deal with the impact of COVID-19 and are now focused on supporting a remote workforce, we want to minimize potential disruptions for customers unable to complete migrations in this timeframe.

As a result, we are suspending the LSA turn-off until further notice. All previously announced timeframes no longer apply. 

This applies to all categories of applications and protocols outlined in our original blog post, including Google Sync for iOS Mail. We’ll announce new timelines on the  <https://gsuiteupdates.googleblog.com/> G Suite Updates blog at a later date.

Despite these timing adjustments, Google does not recommend the use of any application that does not support OAuth. We recommend that you switch to using OAuth authentication whenever possible for your organization. OAuth helps protect your account by helping us identify and prevent suspicious login attempts, and allows us to enforce G Suite admin-defined login policies, such as the use of security keys. See our original blog post for  <https://gsuiteupdates.googleblog.com/2019/12/less-secure-apps-oauth-google-username-password-incorrect.html> details and instructions on migrating to OAuth.  


Getting started 


 

* Admins: No action required. However, we do recommend switching to OAuth authentication. See our original blog post for  <https://gsuiteupdates.googleblog.com/2019/12/less-secure-apps-oauth-google-username-password-incorrect.html> details on migrating to OAuth.

* End users: No end user impact.

* Developers: Update your app to  <https://developers.google.com/identity/protocols/oauth2> use OAuth 2.0 as soon as possible. 

  <http://feeds.feedburner.com/~r/GoogleAppsUpdates/~4/0_2hkD97kQg?utm_source=feedburner&utm_medium=email> 

 


You are subscribed to email updates from G Suite Updates Blog <http://gsuiteupdates.googleblog.com/> .
To stop receiving these emails, you may unsubscribe now <https://feedburner.google.com/fb/a/mailunsubscribe?k=nE9yeTbdE_qNuLKth57ygQMrN6s> .

Email delivery powered by Google


Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States

 




More information about the NFBCS mailing list