Oauth Microsoft PHP error

Rickymundo

I already did that multiple times but I did it again: It says:

But, when saving it says:

KevinTheJedi

That means you are not logging in as the email itself to consent and get the token. The documentation clearly states that when you get redirected to MS you must login as the email you are setting up in osTicket to consent/authorize.

Cheers.

Rickymundo

But that’s exactly what I’m doing. Please keep in mind it was working with Oauth until this morning. Suddenly it stopped. What else can it be?

KevinTheJedi

Rickymundo

Sounds like something changed then. Either on the sever or via the provider.

Cheers.

Rickymundo

How can I figure out what is causing the error: cannot select INBOX, is this a valid transport?

KevinTheJedi

Rickymundo

You really can’t unless you debug the code. The only time I’ve seen this is when using an account other than the email itself to consent/authorize.

Cheers.

Rickymundo

KevinTheJedi But that wouldn't explain the screenshot where in green it says that oauth2 authorization was succesful, right?

KevinTheJedi

Rickymundo

Right but to be fair none of your issue makes sense if you are following the documentation. Make sure you are using official package of v1.17.2 from our website. Make sure you are using the latest build of the OAuth2 plugin. Try going to the database and delete the relevant ost_email_account records matching the email_id of the email having issues. Then you can go in and reconfigure modern auth.

Cheers.

Rickymundo

KevinTheJedi

I wasn't going crazy... ;-)

ramrajone

Make sure your browser cache is cleared, or just use another browser

Rickymundo

Deleted ALL the browser cookies, started in incognito, deleted the app registration and created a new one, tried it on aonther computer. No matter what I do, I keep getting:

Can you please explain to me what the error in fact means?

Legacy login works perfectly. I even went into the mysql tables and deleted references to the account.

cubanp3te

Same issue here, having checked IMAP using other accounts and on different clients, this looks to be a Microsoft issue, although no acknowledgement as yet.

Looks to have started after approx. 19:00 (GMT) on 27th December.

Rickymundo

cubanp3te

Why do you believe that? That really gives me a bit of hope since I was about to lose it....

Found more issue I think might be related:

Link (https://sugarclub[dot]sugarcrm[dot]com/explore/help-forums/enterprise-professional/f/enterprise-professional-questions/6111/group-email-account-not-archiving-from-mailbox)

Another (https://pullanswer[dot]com/questions/collector-not-working-imap-oauth-tag2-bad-user-is-authenticated-but-not-connected)

And another

Farodin

I'm having the exact same issue as well, the oauth2 process works, tokens get refreshed, but no emails are being fetched anymore and the error "cannot select INBOX, is this a valid transport?" pops up every time when trying to save.
I was originally using version 0.2 of the oauth2 plugin, but updating it didn't help.
I can also confirm that the issue started about 2 days ago, with no issues for months before that.

Rickymundo

It looks like an IPv6 issue though, please follow this guide and test it:

https://itsfoss[dot]com/disable-ipv6-ubuntu-linux/

Looks like it's working when I disable IPv6. Can't explain it though...

Farodin

Rickymundo Disabling ipv6 does fix the issue, thanks for sharing!

olimartin

Rickymundo I was having the same issue that has been listed here and several other times.

I had tried ALL other fixes supplied and this was the only one that worked and I can confirm it worked.

Microsoft Support had confirmed to me that nothing had changed on the 27th December (mine stopped working then too). I will let them know this knowledge so they can investigate.

Rickymundo

Where can I claim a bonus? :-)

az68

olimartin
Hi,
Do you have any idea why it worked before 27 ? And what it the role of IPV6 ?

I have the same issue, but i don't have a vps or private server, I don't know if I can disable IPV6 to my host.

olimartin

az68 Honestly - no idea as to why it would suddenly stop supporting IPv6 - perhaps this is something the osTicket devs can look into with Microsoft. From a quick search it seems that IPv6 and Exchange have never gotten on well.. but why it would stop working suddenly over Christmas is strange as my configuration with osTicket worked perfectly prior but it does show a suddent stop at 00:01 on the 27th December 2022.. which is why this issue isn't well documented on here yet.

What are you hosting on? I may be able to help you disable it. For osTicket and it's various plugins etc. I would recommend wither a VPS or using their hosted model as I have used web-hosting services for it before and had constant issues.. AWS Lightsail is a very cheap way of doing it yourself.

bhushan

Hi Kevin,
I have the same error with os ticket. The following links are shown:
https://forum.osticket.com/d/101803-the-requested-url-apiauthoauth2-was-not-found-on-this-server/7
After adding the LDP setting, going to add credentials, and then adding admin credentials, I get a time-out error on my direct URL.
I am using centos 8 and osTicket 1.17.
am added the rewrite permission also on the server.
can you please help me...

KevinTheJedi

MarcinZ Delete the email and re-add it and reconfigure it.

bhushan timeout is indicative of deeper issues. You need to check your logs for any related errors. You can also try deleting the email and reading it. Also, you need to be running v1.17.2 and the latest build of the OAuth2 plugin.

Cheers.