You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently contributionsBB email notification uses smtp email server with username and password for authentication. This will be blocked after Aug 1st and OAuth2 protocols will be necessary. Check this link : https://answers.uillinois.edu/illinois/page.php?id=47591
Acceptance Criteria
Implementing modern authentication for email notifications
The text was updated successfully, but these errors were encountered:
Gmail supports OAuth2. Will need to switch from Office365 to gmail.
Useful resources for implementation are given below:
Run-through for using python library oauth2 Blog on how to send html mails with oauth2 and gmail. Github repo for gmail oauth tools
OAuth2 documentation
Microsoft (Office365) also supports OAuth2, but it seems buggy and will need to use Azure to configure settings. Documentation on how to authenticate SMTP application using OAuth. Documentation on Office365 email setting using OAuth
The current SMTP service can be used. However, will need to switch to Cloud email services later.
Since the current SMTP services will not be affected / blocked by August 1st, moving this to low priority task.
Description
Currently contributionsBB email notification uses smtp email server with username and password for authentication. This will be blocked after Aug 1st and OAuth2 protocols will be necessary. Check this link : https://answers.uillinois.edu/illinois/page.php?id=47591
Acceptance Criteria
Implementing modern authentication for email notifications
The text was updated successfully, but these errors were encountered: