Email_RoundTrip using OAuth2


Userlevel 5
Badge +10

Office 365 has started to block IMAP Basic Auth, with a final permanent on Oct 1st 2022 for all protocols except SMTP. Currently the Email_RoundTrip DataSource in LogicMonitor only supports Basic Auth for IMAP. Has LM or anyone else look at alternate options or attempting to add Oauth2 support for this check? Have others found this check and/or Email_TransitTime checks useful in general?

Thanks!


9 replies

Userlevel 3
Badge +4

Hey @Mike Moniz we're looking at providing Oauth2 support for RTT and TransitTime modules this in the near future. We should have something out ahead of the October 1st deadline.

Userlevel 5
Badge +10

(Now that I regained access to the communities, yippe!)

Any news on Oauth support? I see the O365 cloud datasources have Oauth support but any news on RTT and TransitTime?

Thanks!

Userlevel 3
Badge +3

Hi, @Mike Moniz. We have this working now in our internal labs, so I’m “hopeful” that this will be released in the next 1-2 weeks. 

Any news on when this will be released?

Userlevel 6
Badge +11

Was this ever completed?  I also need to get OAuth2 working for IMAP and an example would be welcome.

Userlevel 3
Badge +2

@mnagel I believe they were released in v179: https://www.logicmonitor.com/release-notes/v-179-release-notes

Office365_Email_OAUTH
Locator: G9F242

Email_TransitTime
Locator: CYPYKY

Email_RoundTrip
Locator: NWJZDX

Userlevel 6
Badge +11

Cool, thanks! Wish I received the release notes via email, but LM will not send them to me no matter how much I try :).

Userlevel 6
Badge +11

Got them, looks hopeful though updated docs would be appreciated by folks I am sure. The current version (from 2020) is a bit outdated (https://www.logicmonitor.com/support/monitoring/applications-databases/email-service-monitoring).  The description lists:

Requires Application Registration & Credentials set.
 - office365.clientid
 - office365.clientsecret.pass
 - office365.tenantid

 

Has anyone used this yet that can map that to what is required for access to a user@FQDN IMAP account? Reading https://learn.microsoft.com/en-us/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth to see how the above are generated.

Userlevel 3
Badge +2

I already submitted an internal doc fixit ticket for the article when I sent my original reply :), so hopefully we can get that sorted in short order. In the meantime I will check with the ME engineer who worked on updating these and get you an answer on the above in the meantime.

Reply