oAuth2 Token lost, after renewal mails aren't fetched

AKBOVG

Hi,

I've an issue, where I don't have a clou what is happening:

We use latest OST 1.17.2. Everything worked fine since we setup the email fetching like in documentation. The Mailboxes are Shared Mailboxes and users got a password, so we can use them.

At 9. January 2022 OST stopped fetching mails. I found out, that the oauth2 Token was out of Date. The automatic renewal seemed to fail.
After reentering the Secret and new authorization it worked again. I was in hollidays in this time, so i can guarantee that there weren't any changes from our side... the System was untouched... I don't have a clou why the Token was not renewed. Has someone else spottet such issues?

Now my problem is: One Account is working fine as aspected. Other Accounts are not. The Tokens are okay now. OST doesn't throw any issues, but it just don't fetch the mails. Any Ideas or hidden protocols how to finde out why the mails aren't fetched anymore?

How can I trigger OST to reauthorize? After changing the oAuth Konfig I don't geht the Microsoft Authorisation Window anymore

RBGE

AKBOVG I had the exact same problem, and it occurred on 8th January (although since that was a Sunday, it wasn't noticed until the 9th). I couldn't see any reason for it as the client secret had not expired, but I'm now wondering if it's possible MS changed something?

As in your case, our issue was resolved simply be reauthenticating, although it was slightly delayed by me accidentally authenticating as myself instead of the shared mailbox. I couldn't see any way to get osTicket to forget the token from my authentication, so had to remove and re-add the whole thing 🤪

AKBOVG

Okay.. I found out, why the mails weren't fetched. I used the wrong user. So it was my mistake, but OST should provide some feedback in this case instead of just don't fetching the mails without any message.

Where the "lost token" problem comes from is still unknown.

KevinTheJedi

RBGE AKBOVG

Tokens can be invalidated by really anything like account changes, password changes, tenant changes, timing mismatch, etc. When I was looking online people had been complaining about this issue with MS for a long time.

Cheers.

AKBOVG

@RBGE I think we are just people who updated very soon after the release, so that it's more about duration as about the exact date.

@KevinTheJedi
Because I don't have such issues with other oAuth2 tools I think there should be a way to make such effects disappear. but I'm not an expert.

For now there are two feature Requests:

Define "Default" Parameters for oAuth2 Authorisation. I have 6 Accounts. All with same endpoints, secret and appid. so it's annoying to type in the same in every account instead of using central default values and just overwrite them if there is really an account in another tenant or something. This would really simplify the setup. I think most users have the same server for their mailboxes used for osTicket Teams.

The other feature is: it would be nice if you add a simple "reauthenticate" button next to the config button in the line of authorisation. You need to change the values to another account and change it back first to trigger the microsoft window again or you need to delete and re-setup the whole mail account. A simple button "reauthenticate" which uses the already safed credentials would help very much and maybe isn't that hard to implement.