Here to confirm that we had the same issue with multiple osTicket instances that we run. The issue began last night and persisted into this morning. Nothing in our environment has changed, these instances have been up for over 2 years (and kept up to date). Granting admin consent did nothing (it was already granted). I ended up getting our instances going again by following the response by @jerer that is marked as best answer on this thread: https://forum.osticket.com/d/105728-ms-oauth2-error-the-api-version-v2-has-been-depreciated
The only snag is that cURL was giving an SSL cert error since we are using certs from an internal CA. I had to append our root cert's public key to the cURL cacert.pem file.
From what I can tell, Microsoft began deprecating the Outlook REST API at the end of March and they have seemingly made it to our org's tenant (as well as many others from the looks of things on these forums): https://devblogs.microsoft.com/microsoft365dev/final-reminder-outlook-rest-api-v2-0-and-beta-endpoints-decommissioning/
mredus
My fix is in that thread:
Yes, we are aware of the deprecations which is why we are working on a new plugin.
Cheers.
KevinTheJedi HI, you have a news for this issue? thanks Marco
I've spent hours if not days on the same issue mentioned in this thread, having the "array ( 'code' => 'Gone', 'message' => 'The API version \'V2\' has been deprecated.', )" error when setting up the email connection to MS O365. Having studied the Guide a thousand of times and followed the instructions carefully, I could not get rid of the error. Then I started studying MS Graph documentation to find that the Resource Detail Endpoint listed in the osTicket documentation is outdated. I changed from https://outlook.office.com/api/v2.0/me to https:/graph.microsoft.com/v1.0/me, and also updated the scopes to "offline_access Mail.ReadWrite" and the Email address attribute to "mail". Then, EUREKA, the error went away and the token tab was added. Unfortunately, when I then try to save the email config, another error occurs. I looked in the database ost_email_account table to find the error being listed as "Credentials: Required option not passed: "access_token". I have no idea what is wrong here. From the error it seems that osTicket is trying to fetch emails from the O365 account without supplying the token. But WHY? Anyone has a clue what needs to be done to make this work? Many thanks! Hans
HansAlbers
Uhh…read my comment above.
