As of June 15th, new volunteers will not be able to access their @scorevolunteer.org (SVO) emails from within the CORE system. This change is prompted by Google security updates that prevent access to applications that only require a username and password to connect to the account without additional verification steps.
Volunteers that have connected their SVO email in CORE prior to this date will be able to continue accessing their emails through CORE until February 21st, 2021. At that time, this feature will be disabled for all users to improve the security of SCORE’s systems.
SCORE has made various updates to assist with this change. These include:
- Adding messages throughout the CORE system notifying users of the upcoming changes
- Updating training documentation and resources
- Adding the ability to send session notes to a client when creating a session
- Removing the automatic reassignment of email mentoring requests after 48 hours
- Eliminating the “48-hour rule” which automatically removed Email as a Mentoring Method if the mentor did not create a session on an email request within the first 48 hours
- Removing the requirement to complete the 010 Business Advice Now course in order to select Email as a Mentoring Method in the volunteer’s profile
All volunteers will continue to be able to access their SVO email account through applications that support a more modern and secure access method called OAuth. Recommended applications to use to access your email, calendar and contacts can be found below.
We will continue to communicate about this change in the upcoming months and provide additional information and resources as needed.
If you have any questions, please email help@score.org.
========================================================================================
========================================================================================
On June 15, 2020, users who try to connect to a less secure app (LSA) for the first time will no longer be able to do so. This includes third-party apps that allow password-only access to Google calendars, contacts, and email via protocols such as CalDAV, CardDAV and IMAP. Users who have connected to LSAs prior to this date will be able to continue using them until usage of all LSAs is turned off.
User instructions
If you are using an app that accesses your Google account with only a username and password, take one of the following actions to switch to a more secure method and continue to access your email, calendar, or contacts.
If you use other apps on iOS or MacOS that access your G Suite account information through only a password, most access issues can be resolved by removing then re-adding your account. When you add it back, make sure to select Google as the account type to automatically use OAuth.
If you are using stand-alone Outlook 2016 or earlier, move to Office 365 (a web-based version of Outlook) or Outlook 2019, both of which support OAuth access. Alternatively you can use G Suite Sync for Microsoft Outlook.
If you are using Thunderbird or another email client, re-add your Google Account and configure it to use IMAP with OAuth.
If you are using the mail app on iOS or MacOS, or Outlook for Mac, and use only a password to login, you’ll need to remove and re-add your account. When you add it back, select “sign in with Google” to automatically use OAuth.
Calendar
We recommend the Google Calendar app [Web/iOS/Android] as the most secure app to use with your G Suite account.
If your G Suite account is linked to the calendar app in iOS or MacOS and uses only a password to login, you’ll need to remove and re-add your account to your device. When you add it back, select “sign in with Google” to automatically use OAuth. Read more
Contacts
If your G Suite account is syncing contacts to iOS or MacOS and using only a password to login, you’ll need to remove your account. When you add it back, select “sign in with Google” to automatically use OAuth.
If your G Suite account is syncing contacts to any other platform or app using only a password to login, switch to a method that supports OAuth.
Comments
0 comments
Article is closed for comments.