-
Notifications
You must be signed in to change notification settings - Fork 456
Open
Description
Hi,
this worked a treat for me for integration with gmail, but I am running into issues with the office365 setup. I followed the instructions, created an app and I was able to generate the token, but the refresh seems to fail:
TokenStore::Refresh: code=400, response={"error":"invalid_request","error_description":"AADSTS900144: The request body must contain the following parameter: 'scope'. Trace ID: 02cde8c3-be9e-45c0-b767-e4c211760100 Correlation ID: 271fa28c-34ce-473f-aaab-e84bfd32c2e8 Timestamp: 2024-08-01 17:44:37Z","error_codes":[900144],"timestamp":"2024-08-01 17:44:37Z","trace_id":"02cde8c3-be9e-45c0-b767-e4c211760100","correlation_id":"271fa28c-34ce-473f-aaab-e84bfd32c2e8","error_uri":"https://login.microsoftonline.com/error?code=900144"}
sasl-xoauth2: TokenStore::Refresh: request failed
sasl-xoauth2: Client::DoStep: new state 0 and err -5
smtp: 8F557F44: to=<sshafiullah@yahoo.com>, relay=smtp.office365.com[40.104.46.34]:587, delay=2180, delays=2179/0.08/1.1/0, dsn=4.7.0, status=deferred (SASL authentication failed; cannot authenticate to server smtp.office365.com[40.104.46.34]: bad protocol / cancel)
I have made sure 'Allow public client flows' is enabled. I did however perform the browser authentication part from another machine since the smtp server is headless. I know it needed to be from the same machine for gmail but was not sure if that is the case for office 365 as well.
Originally posted by @sshafiullah in tarickb/sasl-xoauth2#89
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels