Token Expired

bandre

Hello, I installed OSTicket v1.17-rc3 (34c64f1) and got OAuth working with Azure but the token expired and will not auto-refresh. I have to go into the mailbox settings and click submit to get it to renew. Please let me know if there is something I am missing

KevinTheJedi

bandre

It should be updating when it checks and is outdated. How often are you fetching?

Cheers.

bandre

KevinTheJedi Fetching every 5 minutes with POP

KevinTheJedi

bandre

If you are in test mode they will expire every 7 days regardless.

Cheers.

bandre

KevinTheJedi I have to manually renew the token every time it expires. Just tested it again

Thanks,

KevinTheJedi

bandre

Is it every 7 days? It sounds like you are in test mode.

Cheers.

bandre

KevinTheJedi The tokens expire after roughly an hour and I have to manually renew. I don't believe I am in test mode. Where would I check?
Thanks

KevinTheJedi

@bandre

On the provider end. Not sure why you have to do that every hour. I left mine over the weekend, booted up the server, sent and email, and the token was updated.

Cheers.

effectxd

Hi I'm facing the exact same problems. the tokens is valid only 1 hour and 20 minutes. any idea to solve this ?
tried both migrate version and fresh install osTicket and also recreate API in azure still no luck.
Thanks.

margol

effectxd

Read a MS doc about it:

https://learn.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes#access-tokens

mika_y

We are facing the same problem. Everything works fine while the token lasts but it doesn't get automatically renewed. It gets renewed if an agent answers a ticket or I go and manually click Save changes in the Remote mailbox -tab. But it expires if we just leave it to fetch emails.

KevinTheJedi

mika_y

See here:

https://github.com/osTicket/osTicket/issues/6299#issuecomment-1280691404

Cheers.

Jedi_Jr

We are facing the same problem. Everything works fine while the token lasts, but it doesn't auto-renew. It refreshes when I manually click Save Changes on the Remote Mailbox tab. But it expires if we leave it just to fetch emails.

KevinTheJedi

Jedi_Jr

Then it doesn't sound like you have cron running. Or maybe you are using a localhost domain that the cli is not liking.

Cheers.

soportelinea

Hello.
could someone solve this problem?

KevinTheJedi

soportelinea

Are you all the way up to date with v1.17.2 and the latest build of the plugin? Did you have to grant special permissions when getting the initial token and then revert those settings afterwards? Do you have a successful cron running? Do you see any errors in the system logs? Can you go to the OAuth2 Config popup and get a new token?

Cheers.

sabahsawor

I do have the same issue here and this is my cron.php file

and my api.inc.php

Any idea ?

KevinTheJedi

sabahsawor

That information is irrelevant to this issue.

Cheers.

Boephe

https://github.com/osTicket/osTicket/issues/6299#issuecomment-1280691404

This link posted by KevinTheJedi suggests a few things:

Make sure you haven't signed into the M365 account with a Temporary Access Password. Even if the account uses 2FA, just do a regular 2FA sign in.
Make sure CRON is using the same PHP version as your application. You can have multiple versions of PHP installed side-by-side and CRON can be pointing to the wrong one. I don't actually know how to check but I assume Google does since other people managed to fix it.
Helpdesk Audit Plugin being out of date (and any other plugins). Make sure all plugins are updated when you update osTicket.

mudslide567

We have been running this successfully pretty much from the inception of 1.17 (i.e. several months) without any issues. Until the day before yesterday (1/16/23). Everything stopped with the dreaded token expired message. We renewed it but the new token showed it expired in 24 hours.
Now we have to monitor the token.
Talking of tokens, what's with the reCaptcha token that expire before you can type 3 lines on this forum?

KevinTheJedi

mudslide567

Anything on MS end can invalidate the token and unfortunately it requires you to manually consent again to get a new one. Typically token regeneration is automatic but if MS invalidates the token there is nothing you can do but get a new one.

The token expiration is expected as we get a refresh token and once the access token is expired we use the refresh token to get a new access token automatically.

Talking of tokens, what's with the reCaptcha token that expire before you can type 3 lines on this forum?

Huh?

Cheers.