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

OAuth2 error "This API version has been deprecated"

pcps

Hm, not working for me. How long did you wait for effect the role asignment?
I am waiting for hours now.

PeteB

This was all working for me for 2 shared mailboxes yesterday (although using the entra ID accounts associated with them, but now today when I try to add a 3rd using the exact same method, it won't work and I get the error above:

array ( 'code' => 'Gone', 'message' => 'This API version has been deprecated.', )

What's worse, is when I tested one of the other shared mailboxes by deleting the token, that one is also no longer working - settings unchanged.

I've tried unticking the strict matching and using an account (with it's own mailbox and license) that has full delegation (send and full access) but I'm still getting the error

I've even tried using an account with Global Administrator, that can access the mailbox via owa, has full send+manage permissions, has Application Administrator on the app, and still same error

(Application also has admin consent granted - clicked on several times today just to make sure)

OSTicket: v1.18.1 (0375576)
Oauth2 plugin: 0.6

jgallott

Went to permissions on the app, clicked 'grant permissions' and confirmed as an admin (although the permissions had already been granted 1.5 years ago).

Incognito mode in chrome to the mailbox config. Clicked 'submit' to renew token, Signed in as the mailbox owner (which has application admin role) was asked to grant permissions, looks to be successful, but gets the error displayed in OSTicket.

The OAuth plugin is 0.6 version. Is it possible there really is a deprecated API?

KevinTheJedi

jgallott

Doubt it as I was able to setup my email with no issues.

Cheers.

mfrlchris

Our user is a User is fully licensed unshared email.
User: no unsuccessful logins per Entra sign-in logs
User: consent to application success (no failures of any kind in Entra Audit Logs)
Manually assigned user as Application Admin in Entra
Added (via Entra) openid and profile permissions to the user just for fun
Waited overnight.
Still no love.

KevinTheJedi

PeteB mfrlchris

I'm still waiting for apuhm to confirm what he did exactly to see what the issue was exactly.

Cheers.

KevinTheJedi

mfrlchris

Curious, is IMAP enabled for the mailbox? Was IMAP - AccessAsUser.All added to the Application Permissions and did the Application Admin (or Tenant Admin) provide consent for all permissions?

Cheers.

KevinTheJedi

PeteB mfrlchris

Also, are ya'll using government O365 accounts or standard account?

Cheers.

PeteB

I wonder if M$ have deprecated something in the last 24 hours or so, I'm using the same user as yesterday, and it was working fine, but getting this deprecated error message today. This whole move to OAuth2 has been so frustrating for us!

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)

PeteB

Not sure what a government one is? We buy O365 tenant and a bunch of E5 licences from a reseller
IMAP is enabled in Exchange online for all accounts and API permissions have it:

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.

« Previous Page Next Page »