Replies: 2 comments 1 reply
-
When big tech crapped on the last authentication system killing my community portal entirely, I run nothing but stock authentications so I don't run into future snags they create along the way since I (and the community) dont have quick response times to fixing issues like this. I tried to work with all big tech, they all shut me down after good faith in them. I wish you the best! |
Beta Was this translation helpful? Give feedback.
-
Are there any plans to implement this? https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online Also, Microsoft provides this flow to implement and set up SMTP on OAuth2: https://learn.microsoft.com/en-us/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth |
Beta Was this translation helpful? Give feedback.
-
Hi,
on the 1st of October 2022 Microsoft is going to discontinue Basic Authentication in favour of OAuth2. This will affect any service that is currently using Office 365 to send "unattended" email. I have already incurred in this issue on one of my services (not DNN) where one day it was working like a charm and the following day stopped working not being able to login O365 to send emails (but fortunately I was still in the grace period and I just re-enabled Basic Authentication on my Tenant to temporarily fix it).
Now, the point is that if one wants DNN to send emails (such as notifications, alerts, etc.) via O365 he/she will no longer able to do so using the current (as far as I know) Mailkit APIs available in DNN. Mailkit itself seems to have limitations in supporting OAuth2 with O365 (https://github.com/jstedfast/MailKit/blob/master/ExchangeOAuth2.md). For sending unattended emails is of course out of question the use of MFA since DNN runs as a service (no user seats in front of that installation ready to insert user, password and codes sents during the multy factor authentication). The only viable solution I have found and tested so far, is to create what Microsoft calls in its documentation a Client Credentials Flow (https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-client-creds-grant-flow) and use Graph APIs to send emails instead of MailKit.
I'd like to know if the comunity is aware of this next to coming issue and if there are already plans to fix it.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions