OAuth2 error "This API version has been deprecated"

apuhm

We have created OAuth2 in Office 365 according to the "Microsoft Authorization Guide" unfortunately we get the following error when adding it: array ( 'code' => 'Gone', 'message' => 'This API version has been deprecated.', )

KevinTheJedi

apuhm

What does your OAuth2 configuration look like? Also, what does your App Registration look like in Entra ID?

Cheers.

apuhm

we have set this

KevinTheJedi

apuhm

Most important thing is the plugin config. What does that look like?

Cheers.

apuhm

in osTicket we configured this:

KevinTheJedi

apuhm

Hmm, that seems right. Contact your tenant admin to see if they disabled the Outlook API or something.

Cheers.

KevinTheJedi

apuhm

FWIW, I just retested a new app creation/setup and signing in with my O365 account and did not encounter any issues.

Cheers.

apuhm

You're right KevinTheJedi, it was an issue with authorization in Entra ID. It looks like mail users in osTicket need the right application admin. And now we know, that mail alias adresses are not supported.

It is now working and fully functional, issue solved.

Cheers and have a nice weekend 😃 🍻

ElectricB0i

Hi there, we seem to be having the same exact issue you were having. We keep getting
array ( 'code' => 'Gone', 'message' => 'This API version has been deprecated.', )

apuhm I see your answer but I am not completely sure I understand what I am supposed to do or change in Entra ID. Some help with this would be amazing!

KevinTheJedi

ElectricB0i apuhm

Is that what y'all meant? Y'all made the Shared Mailbox an Admin? If so, that's not really a good idea. Instead you should revert those changes, delete the existing Token you got for the email (within osTicket - Remote Mailbox tab, click Config, click Token tab, click Delete Token, confirm the deletion), and follow the steps below:

https://forum.osticket.com/d/104878-oauth2-email-fetch-and-send/4

Note, we will be updating our O365 OAuth2 Authorization (Email) Documentation soon to include the new "Azure AD" -> "Entra ID" verbiage changes as well as section for detailed instructions on how to configure a Shared Mailbox/Resource Email.

Cheers.

KevinTheJedi

PeteB mfrlchris

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

Cheers.

llovet

I have the same issue and verify at least the same steps are sharring but cannot enable, @KevinTheJedi can you share what access permision additional we need to setup and the emial attrbute the correct one. Also as part of this note i dont have a Entra ID license paid, i hve the license commming with office 365 and i have around 450 mailboxes manage.

KevinTheJedi

llovet

Is it a shared mailbox?

Cheers.

ElectricB0i

@KevinTheJedi
Update: It seems that giving Application Administrator to the shared-mailbox user allowed it to work properly. The reason it wasn't working before was that it needed some time to work after giving it the role. I did this through Entra ID and it seems to be working fine.

mfrlchris

I hate to be the dumbest kid in the room, but I'm just not having any luck.
I'm getting the same error as shown in the first screenshot of this thread.
This is my second, totally separate OST install from different servers on my premises to the same MS365 tenant (different email addys of course). The other OST install was just a couple of months ago. Thus, I have a very similar good version to compare with.

Email account being used is a real UserMailbox, so I shouldn't have to do anything special as mentioned in KevinTheJedi https://forum.osticket.com/d/104878-oauth2-email-fetch-and-send/4

What else causes this error? I've been known to overlook things, despite diligence...
Thanks!

osTicket Version v1.17.5 (7c20036) — Up to date
Web Server Software Apache/2.4.52 (Ubuntu)
MySQL Version 8.0.36
PHP Version 8.1.2-1ubuntu2.17

mfrlchris

I'm running into the same issue. I've set up another instance a few months ago, so I'm hoping I've missed some of the common pitfalls. Short answer: Email address belongs to a fully licensed non shared account. More details and settings to follow.
Edit: was going to follow your steps above, but Token tab does not exist.

KevinTheJedi

mfrlchris

Then you're good to follow the steps. They need to delete tokens as they've already did something else to retrieve a token. Since you don't already have one simply follow the steps I linked above.

Cheers.

KevinTheJedi

mfrlchris

Maybe go to enterprise applications, approve and consent on behalf of the organization as an admin, wait for the changes to take affect and retest.

Cheers.

jgallott

We are just getting this. This is an OSTicket installation that has been going for a year and a half. We have on occasion had to manually refresh the token, but that has always gone smoothly. This is an M365 user mailbox, no MFA, Application Admin role, but this time when the token expired it gives that 'array ( 'code' => 'Gone', 'message' => 'This API version has been deprecated.', )' error.

There is not an option to delete the token in the config for the mailbox in OSTicket.

jgallott

sign-in log
May 28, 2024 at 5:04 PM
Failure
The user or administrator has not consented to use the application with ID '{identifier}'{namePhrase}. Send an interactive authorization request for this user and resource.

KevinTheJedi

jgallott

Exactly what I suspected. In that case do what I said above and go to Enterprise Applications, click the Application, approve and consent on behalf of the Organization as an Admin, wait for the changes to take affect, clear all browser cache/cookies/sessions (or use incognito window), and retest.

Cheers.