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

OAuth2 error "This API version has been deprecated"

mfrlchris

KevinTheJedi
IMAP enabled is a default tenant email policy.
IMAP - AccessAsUser.All was added to the Application Permissions
Performed by Tennent Global admin.
License is MS 365 Business Basic (Nonprofit Staff Pricing)

jhigdon

We are getting this same issue. Not setting up new emails, just trying to re-auth emails we've had set up for years now. Getting the API version Depreciated message on all the emails we're attempting to re-auth.

Not sure if it's related but I did see Microsoft is depreciating some API's in a few days on the 1st.
https://learn.microsoft.com/en-us/azure/api-management/breaking-changes/api-version-retirement-sep-2023

PaulCVicForms

Just to add in here that we are experiencing the same issue now. The User account used has an "Exchange Online Kiosk" licence for the mailbox. It has Application Admin role and the API permissions are as below:

jgallott

Yes, IMAP - AccessAsUser.All is part of permissions, and IMAP is enabled for the user.

Possible MSFT is deprecating in a rolling manner.

Not Government license.

Schusti83

I've been running an Osticket system for over 2 years. There's never been a problem with it. This week I wanted to set up a new second one and am having the same problems as you. All of your suggestions didn't help. The system is configured 1:1 like my first one, I have now reinstalled it 3 times and configured all the settings. It's strange that so many people are having this problem recently. But it only affects new installations. As a test, I installed 1.17.x, which I started with back then.

jgallott

@"Schusti83" Not just new installs. Ours has been up since December 2022

BaneTBI

I'm having the exact same issue, been using the same email account for the last couple of years and when I went in to reauthorize I'm getting the array ( 'code' => 'Gone', 'message' => 'This API version has been deprecated.', ) error.

Schusti83

and you wanted to re-auth the email addresses now? The secret key for my first system is valid until September. then I would have to re-auth it too. OK, I won't do that on the first system at the moment... Then I strongly assume that the apis expiry has something to do with the link posted by you. Then we can only hope that there will be a new version of the plugin for osticket soon.

BaneTBI

Schusti83 I didn't want to, but it expired and when I went to reauthorize I got the error. 🙂

Andy_B

I upgraded to 1.18.1 of OST and 0.6 of the Oauth plugin as I was using an older version, I can now get to a point where when I submit the config it asks me to pick an account, but it just goes back to the config screen with the same error everyone else is seeing.

DSprag

I'm afraid we're having the same issue - all was working well until 11am this morning..
No issues found in any of the azure logs, sign-in etc. all looks fine, lots of 'sucesses'.
I've been through and added in the Application Admin, but looking at the above it feels unlikely that will resolve the issue.

DSprag

DSprag specific error :

[GMT_MailList] Error: An error occurred with the following error message: "Validating connectivity via endpoint /me/MailboxSettings failed. Details:

{"error":{"code":"Gone","message":"This API version has been deprecated."}}".

PeteB

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

berhane

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

bfernandes

Hi guys, any news about that?

I steel with the same error:

KevinTheJedi

Jesus i hate microsoft.. I'll have to see if I can replicate this.

ppcm

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

jgallott

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.

bfernandes

I have already tryed to delete APP, create new APP, change account email, but the error is the same.

jfields

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.

« Previous Page Next Page »