![]() I don't use Google services, but something I read suggested that users who don't want to change to email clients that support OAuth (I'm not sure which ones do, I suspect such support remains uncommon in the "desktop" space at least) may have two options. Some specific searches for related discussions on email protocols and contexts would be the next step. Some general reading about Basic Authentication vs OAuth and alternatives may help you get your bearings. OAuth is one of the approaches that is meant to address some of these issues. Often, substantially different types of services are accessed through the same set of credentials, which means a compromise in one area (such as email) can affect something else (such as general purpose file storage). Often, servers don't implement robust (and user tunable) methods of gating clients based on IP Address and/or other means. All client applications and devices use the same credentials each time they have to authenticate. The client stores, and passes to the server, plain user/pass info. ![]() There are some issues with Basic Authentication, at least the way it is normally implemented. Google is: 1) actively discouraging what's known as Basic Authentication, and possibly some other less basic methods from the sound of it, while 2) actively encouraging the use of OAuth2. Click to expand.There are a number of ways an email client can authenticate to an email server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |