With this release, apps can use one of the following OAuth flows to authorize and get access tokens on behalf of a user.įollow these detailed step-by-step instructions to implement OAuth 2.0 authentication if your in-house application needs to access IMAP and SMTP AUTH protocols in Exchange Online, or work with your vendor to update any apps or clients that you use that could be impacted. This functionality is built on top of Microsoft Identity platform (v2.0) and supports access to email of Microsoft 365 (formerly Office 365) users.ĭetailed step-by-step instructions for authenticating to IMAP and SMTP AUTH protocols using OAuth are now available for you to get started. This feature announcement is for interactive applications to enable OAuth for IMAP and SMTP.įor additional information about non-interactive applications, please see our blog post Announcing OAuth 2.0 Client Credentials Flow support for POP and IMAP protocols in Exchange Online.Īpplication developers who have built apps that send, read or otherwise process email using these protocols will be able to implement secure, modern authentication experiences for their users. If the client can't establish SSL with the server it can't authenticate. No idea what the issue is in your case, but sometimes older software doesn't stay compatible when servers upgrade SSL and deprecate older versions of SSL being used by older software. Today, we’re excited to announce the availability of OAuth 2.0 authentication for IMAP and SMTP AUTH protocols to Exchange Online mailboxes. .com/r/Thunderbird/comments/y24wrw/office365authenticationproblemsnew/ The current version of Thunderbird is 102.3.2.
Ever since we announced our intention to disable Basic Authentication in Exchange Online we said that we would add Modern Auth (OAuth 2.0) support for the IMAP, POP and SMTP AUTH protocols.
0 kommentar(er)
