OAuth2 error "This API version has been deprecated": Page 6

OAuth2 error "This API version has been deprecated"

danielbalog

I can confirm it works here, too (Germany). I changed nothing in the Exchange Admin area so I doubt it has anything to do with the settings there.

PeteB

Yep, confirmed working for me too now, just by magic - Thanks M$ 🙄

Also a big thanks to everyone looking at this here too

BaneTBI

Mine is working now too.

KevinTheJedi

Thankfully they reverted/fixed it but sucks it took so long. Also sucks they didn’t notify anyone so we all thought it was something else. Good ole Microsoft. Gotta love em.

bfernandes

Hello everybody. I configured the email correctly, a token was generated normally, however all emails remain in the inbox and are not being downloaded by the ticket system.

I checked the settings and it is set to download every 5 minutes, but it doesn't. no errors are generated.

I did the email sending test and was able to send it normally.

can you help me

KevinTheJedi

bfernandes

You need to create your own discussion. Your issue is not relevant to this thread.

Cheers.

bbertling

currently having this issue. i am trying play with the exchange settings and mailbox settings. i have the EAC set with turn off smtp auth protocol, unchecked. i went to the account and unchecked smtp auth, and then set it again 10 minutes later... what am i missing?

previously existing setup, token expired so i went to refresh, now getting the api v2 deprecated message.

double checked the mailbox settings, nothing changed. created a new token and secret, recreated the email in OSticket.

i removed the global setting as stated above, i disabled smtp auth on the account, left it for an hour. switched it back to on, less than 30 minutes, but still not working.

BingoBongo

I currently have the same problem after reinstalling the plugin. Have double and triple checked all configurations but have had no luck so far. Are we at the mercy of Microsoft again?

KevinTheJedi

BingoBongo

Shouldn’t be, everyone else’s is working minus you and two others (one of which is government o365).

Cheers.

preseznik

We got this issue.
I applied this fix, even though the person posting says it didn't work:

User Details: https://graph.microsoft.com/v1.0/me
Scopes: offline_access https://graph.microsoft.com/Mail.ReadWrite
Email Address attribute: mail

Seems to be fine? Reading further replies seems to suggest no, but this at least refreshed the token and got rid of the "V2" error from the OP in this thread.

mredus

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/

KevinTheJedi

mredus

My fix is in that thread:

https://forum.osticket.com/d/105728-ms-oauth2-error-the-api-version-v2-has-been-depreciated/41

Yes, we are aware of the deprecations which is why we are working on a new plugin.

Cheers.

f07pd

KevinTheJedi HI, you have a news for this issue? thanks Marco

HansAlbers

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

KevinTheJedi

HansAlbers

Uhh…read my comment above.

Cheers.

« Previous Page