If a bad actor got access to your username and password (for example, if you re-use the password on another site that is subject to a data breach), they could access your account data with just that username and password information through an LSA. That’s because LSAs provide a non-Google app access to your account through just a username and password, without any other authentication factor. When account access is provided through an LSA, it puts that account at risk of hijacking. This provides users with more options, and helps users get work done in a way that works well for them. For example, you may give the iOS mail app permission to see your work email. Why this matters Many users use non-Google apps, and give those apps permission to access G Suite data. See below for more details on the possible impact of this change, and some recommendations for change management with users of LSAs. This is a continuation of our previously announced process to limit access to less secure apps to protect G Suite accounts.
After JUsers who try to connect to an LSA for the first time will no longer be able to do so.That email includes a list of users who are likely to be affected.Īccess to LSAs will be turned off in two stages: We’ve also emailed your organization’s primary admin with details around this change. This is most likely to impact users of legacy email, calendar, and contacts apps-see below for more details. Instead of LSAs, you can use apps that support OAuth-a modern and secure access method. They make your account more vulnerable to hijacking attempts. LSAs are non-Google apps that can access your Google account with only a username and password. What’s changing Starting in June 2020, we’ll limit the ability for less secure apps (LSAs) to access G Suite account data.
0 kommentar(er)
