MS OAuth2 Error: The API version 'V2' has been depreciated.: Page 3

MS OAuth2 Error: The API version 'V2' has been depreciated.

jerer

KevinTheJedi
This is weird, things work fine for me at the moment (after removing the call to the user endpoing API). Did you forget some other scopes there? (like openid, User.Read, etc.).

Can only use offline_access and https://outlook.office.com/XXXXXX scopes or IMAP/SMTP/POP authentication fails.

KevinTheJedi

jerer

That's exactly what I used offline_access https://outlook.office.com/IMAP.AccessAsUser.All https://outlook.office.com/SMTP.Send.

Cheers.

KevinTheJedi

!!! ANNOUNCEMENT !!!

Everyone still experiencing this issue:
Please retest after following these instructions to see if it starts working again:

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

Once I get enough confirmations that the changes work I'll make the changes official.

jerer

KevinTheJedi
Although I already bypassed it the other way, I still would like to confirm I tested this modification and it works. Thanks for looking into this!

archercentauri

KevinTheJedi Hi Kevin, My brain hurts after such a long day... I will however try tomorrow and come back to you. Thanks for your assistance in advance.

LucaBallBCPOP

KevinTheJedi I'm confirming your proposed change does work with a businessaccount.

RBGE

KevinTheJedi Just to add another confirmation, this modification worked for me when using a shared mailbox. However, I did log into the shared mailbox directly (yes, I know - not best practice but it works), so I'm not sure this provides any additional information for confirmation of a fix 😐️

Thanks for the modification! I suspect a lot of people will have expired client secrets around now given it's just over 2 years since the plugin was released!

rodrigocaicedo

KevinTheJedi this fix works on my end, at least to register a new email address using microsoft oauth2. I haven't test yet if it receives and sends email, but at least it allowed me to save the email.

asmith3006

KevinTheJedi ~~This worked for me.~~

~~This authenticated for me, but isn't actually pulling any emails through :-(~~

Edit2: This actually DOES work for me. I had no emails coming through for about an hour (on this mailbox, other mailboxes continued to work) and then as if by magic they started flowing through!

JoePearse

KevinTheJedi Can confirm this worked for me.

magagninos

KevinTheJedi I just apply your instruction to my osticket instance and it's now work fine. Thanks a lot!

KevinTheJedi

jerer

So I’m assuming my account is just fucked up then. Because I always had a dev account but it expired so now I’m using my personal account and this is the one that’s not authenticating (yes I created a brand new registration using the personal account, etc.). I contacted MS to see what’s going on so unfortunately I’m at their mercy. Glad my changes are working for you though. Once I get more confirmations I’ll clean it up and make it legit.

Cheers.

jfields

I've modified the plugin... What other settings should we use for the Auth, Token and Scopes?

KevinTheJedi

jfields

Same everything just do the modifications listed in the post.

Cheers.

jfields

KevinTheJedi,

I get an AUTHENTICATE failed using the same settings but modifications to the plugin.

KevinTheJedi

jfields

That’s the same thing I get but @jerer says otherwise. Maybe try offline_access https://outlook.office.com/IMAP.AccessAsUser.All https://outlook.office.com/SMTP.Send for the scopes?

Cheers.

jfields

array ( 'code' => 'InvalidAuthenticationToken', 'message' => 'Access token validation failure. Invalid audience.', 'innerError' => array ( 'date' => '2024-10-01T20:38:46', 'request-id' => '<guid>', 'client-request-id' => '<guid>', ), )

KevinTheJedi

jfields

That sounds like something isn’t configured correctly. Do you have all of these scopes added and admin consented in the app registration in entra?

Cheers.

jfields

KevinTheJedi,

This is the third account I'm setting up for this application. The previous two work fine because their token hasn't expired yet (and I'm tiptoeing around it). I can get it to authenticate just fine but then get AUTHENTICATE failed when trying to download IMAP mail.

For as big as Microsoft is, you would think they would not change things so often or so quickly.

jfields

KevinTheJedi,

To get it to authenticate successfully (but fail on fetching email (AUTHENTICATE failed)) I used:
Resource: https://graph.microsoft.com/v1.0/me
Scopes: offline_access https://graph.microsoft.com/IMAP.AccessAsUser.All
Mail Address Attribute: mail

To get it to give me the invalid token error:
Resource: https://graph.microsoft.com/v1.0/me
Scopes: offline_access https://outlook.office.com/IMAP.AccessAsUser.All https://outlook.office.com/SMTP.Send
Mail Address Attribute: mail

I believe this is because I'm calling scopes that are different than the Resource URL I'm reaching to get the mail attribute.

KevinTheJedi

jfields

But if you modified the plugin and database records appropriately it shouldn’t call the endpoint at all. You can try deleting the existing token via token tab in authentication config and changing the user endpoint to “ https://outlook.office.com/api/v2.0/me” and email attribute to “EmailAddress”.

Cheers.

KevinTheJedi

jfields

Do you have @outlook.com addresses or a business account with a custom domain?

Cheers.

ognalysis

KevinTheJedi In the event someone else doesn't, I do.
We're dead in the water with the API broken, handling tickets manually.

KevinTheJedi

ognalysis

Please go ahead and test.

Cheers.

ognalysis

With the given workarounds, what is the reversal if MS ends up fixing this? I'm hesitant to make direct changes to the PHP/database without a fallback.

KevinTheJedi

ognalysis

The reversal would be to replace the unpacked plugin with the latest download from the website, reversing the db changes, and that’s it.

Cheers.

ognalysis

KevinTheJedi I'm not this familiar with php, is it as simple to just repack the plugin instead? If so, it makes sense to me that it'd be easier to unpack, modify, and then repack the plugin instead of modifying the DB.

« Previous Page Next Page »