oAuthV2 Expired Token Can't ReAuthorise

rwilson

Hi All,

We are currently running osTicket v1.17.2 and oAuthv2 v0.6.

We've had osTicket working seamlessly for a few months now but yesterday morning our oAuthv2 token with MS expired. It seems this is due to a bug with the plugin not auto-refreshing the token but that's fine.

When I hit submit in the config for my email address it takes me through the MS login as normal but then redirects to our ticket helpdesk homepage rather than back to the email with the confirmation. I understand this can be caused by things like URL rewriting not being activated or setup correctly but this is all correct. This worked for me in the past but now seems not to be.

Has anyone else faced this issue or has any clues on how to get around this?

Thanks in advance!

KevinTheJedi

rwilson

It does auto-refresh the Access Token however only MS gives you a new Refresh Token and we didn't know that at first (not well documented). However, this will be addressed in the next release so stay tuned.

Being redirected to the homepage typically means you either have the wrong OAuth2 info in the email config or the URL you are using does not match the Redirect URI in osTicket and in the registered application.

Cheers.

KevinTheJedi

rwilson

You should also use an incognito/private window to make sure it's not attempting to use the wrong account to authorize.

Cheers.

AlanF

KevinTheJedi

Any ETA on the next release? I just discovered that our tokens are expired on two instances of OSTicket and emails have been failing for a while now. We're also having issues with the LDAP authentication and user lookups, so I'm hoping those fixes are in the next release as well.

rwilson

KevinTheJedi
Hi Kevin, Thanks for the quick response.

This is the Redirect URI in Azure:

and the URL in osTicket:

All the information in the email config is the same apart from I had to generate a new secret as we didn't store the old one anywhere.

Would you recommend remaking the azure app registration and reconnecting that way?

Cheers,

KevinTheJedi

rwilson

Then you probably used the Secret ID and not the Secret Value.

Cheers.