"AUTHENTICATE" failed despite successful OAUTH request and token

teward001

After beating my face against the OAuth API of Microsoft for an eternity, I finally got OAUTH2 tokens to work. However, when I enable Email Fetching, and the system attempts to IMAP AUTHENTICATE, it fails to AUTHENTICATE and therefore can't pull emails. Which sounds like a Bug.

It's using a token that expires in an hour, I'm not sure if that token expired, or if the MS365 side of things for the given user mailbox is a problem, has anyone else encountered this and have a solution to this? Note we don't seem to ahve a way to 'forget' the last OAuth token in case that got invalidated by MS for some reason.

KevinTheJedi

teward001

You probably didn’t setup the registered app in azure appropriately or maybe configured the email config incorrectly. I would follow our documentation and retest. Don’t mess with the scopes or resource owner endpoint keep those as the defaults we provide. The only thing you need to change is the client id, client secret and the authorization/token endpoints.

Cheers.

teward001

KevinTheJedi Then you have a larger problem. The Outlook API you guys refer to in your scopes is Deprecated, and officially dies in November 2022. If you don't have a solution that uses the Graph API then you will be fully screwing everyone. Microsoft's API documentation even indicates that that API is deprecated

KevinTheJedi

teward001

We are already looking into the new API. We followed their documentation and this is the only way we could get it to work appropriately.

Also, don’t be nasty.

Cheers.

KevinTheJedi

teward001

The scopes and stuff are not hardcoded, as you saw, you can change them to your liking. If you use Graph to get the token and that doesn’t authenticate to Outlook then you need to contact Microsoft to see why that is.

Cheers.