Not anything to do with this is it? https://learn.microsoft.com/en-us/answers/questions/1611326/deprecation-of-outlook-web-api-imap-oauth2-authent
We are seeing the same problems with OSticket/v1.17 + Oauth2/v0.6 plugin configured with Microsoft Oauth2. The automatic token renewal for "Remote Mailbox" access fails with "array ( 'code' => 'Gone', 'message' => 'This API version has been deprecated.', )" error. The token for "Outgoing (SMTP)" using the same Microsoft Oauth2 is renewing just fine though.
A colleague suggested that a switch to Graph API instead of the Outlook API may be necessary: https://learn.microsoft.com/en-us/outlook/rest/compare-graph
However, I have not seen documentation on using Graph API in the documentation here: https://docs.osticket.com/en/latest/OAuth2/Microsoft%20Authorization%20Guide.html
Hi guys, any news about that?
I steel with the same error:
Jesus i hate microsoft.. I'll have to see if I can replicate this.
Hello guys, one more on my side, same issue since this afternoon KevinTheJedi If you can't replicate on your tenant, contact me in private to use my own
You may need to connect to a tenant that is experiencing the problem. If it is a gradual rollout, your tenant may not be affected yet.
I have already tryed to delete APP, create new APP, change account email, but the error is the same.
I changed some of the URLs and got a different error:
Invalid mail attribute
I changed the User Details: https://graph.microsoft.com/v1.0/me Scopes: offline_access https://graph.microsoft.com/Mail.ReadWrite Email Address attribute: emailAddress
Since the outlook API is depricated, they suggest moving over to the Graph API. I just don't know what email address attribute it should use. I do not get any authentication errors.
I got it successfully authenticate. I changed the Email attribute to 'mail'.
Only time will tell if it successfully gets the emails. I will report back.
Jeff
It says it's authenticated correctly but when I go back to the page, it says there's an error authenticating. Perhaps it's not as simple as changing the URL and a few scopes.
jfields
Exactly. We are looking into it. Their docs say only the endpoints changed and when updating them getting a token is fine but authenticating is failing. Microsoft really sucks ass..
Cheers.
KevinTheJedi Thank you for what you do. We have an organization that has come to appreciate the ability to send in emails for tickets and reply and appreciate it even more as it came crashing to the floor.
KevinTheJedi Too bad the emoticons don't include a beer, a cake or even a pie, or I'd send you one. Appreciate the effort.
I'm at the mercy of ms at this point...waiting to hear back from them. If any of y'all would like to reach out to them on your own behalf to ask what changed and how to debug actual imap login issues that'd be great. I'm getting nowhere with them so far..(as always) Nothing is appearing in the (Microsoft) logs neither. Simply get an Authenticate failed message from the outlook server and nothing else.
Strangely this morning I thought I would just try again to see if anything had changed, I managed to sucessfully authenicate and can see new tickets coming in.
@Andy_B I tryed on my side too, and it works, no modification in the setup since yesterday Does MS correct something on their side?
@ppcm By "no modification since yesterday" you mean the original settings? I have tried on my side, too, but it still fails with the "deprecated" error. Could you share a screenshot with the exact settings which are working for you?
danielbalog Exactly, the original settings, in osTicket side and in MS side @Andy_B was faster for the screenshot ;-)
No luck for me yet... but I am on my first cup of coffee so I'll try again in a bit...
