Updated oAuth2 wrong file on download page?

HansAlbers

Was deperately waiting for this and happy it is now release. Downloaded the 'new' oAuth plugin but it appears to be the same as before. The file compares as being 100% the same as the one we already have installed and it also still reports being version 0.6. Could there be a little mistake made on your download page?

Thanks! Hans

KevinTheJedi

HansAlbers

Version is same, but contents are not. Open the PHAR file with a text editor and search for "TEMP:". If you see that then it's the new plugin.

Update:
I just tested myself and it is indeed pushing the latest plugin. So either yours is cached or something else. Try incognito window, etc.

Cheers.

HansAlbers

I checked the file and it has the TEMP: in it, line 20883. I did replace the plugin file in our include/plugin directory after having renamed the old one with an .old extension.

Per your instruction would need to use this for the Scopes:
offline_access https://outlook.office.com/IMAP.AccessAsUser.All https://outlook.office.com/POP.AccessAsUser.All https://outlook.office.com/SMTP.Send
but this results in:

I changed Scopes to:
offline_access IMAP.AccessAsUser.All POP.AccessAsUser.All SMTP.Send

and then it successfully authenticates (after having submitted my email address) and gives me a token tab. However, saving the email settings, after enabling the Fetching, still results in an authentication failure.

Any ideas welcome. Cheers,

KevinTheJedi

HansAlbers

Because that's not the right scopes. When you remove the URL prefixes it uses graph (I believe) which isn't going to work. Please follow the below EXACTLY as I type it:

Login to osTicket in an incognito/private window
Go to the email in question
Click Remote Mailbox tab
Set Authentication to OAuth2 - Microsoft
Click Config
Copy the Redirect URI
Go to Azure Portal
Go to Entra ID
Manage > App Registrations
Create a BRAND NEW app registration using SINGLE TENANT
Set Web redirect uri with the redirect uri from the email config you copied earlier
Create the app
Go to Certificates and Secrets
Create new secret
Copy and save the SECRET VALUE
Click Overview in app registration
Copy the Application (client) ID
Paste that into the Client ID in osTicket
Paste your client secret value into the client secret in osTicket
In the overview section at the top of the app registration click the Endpoints button
Copy the OAUTH2 V2 AUTHORIZATION endpoint
Replace the Authorization Endpoint in the email config
Copy the OAUTH2 V2 TOKEN endpoint
Replace the Token Endpoint in the email config
Submit the popup
Login AS THE EMAIL YOU ARE CONFIGURING IN OSTICKET
Consent to the permissions
You should be good

Cheers.

HansAlbers

So then I also leave Resource Details Endpoint to what is was before and pre-filled in as:
https://outlook.office.com/api/v2.0/me

Unfortunately that brings me back where I was before, not even getting a token:

Thanks!

KevinTheJedi

HansAlbers

So you shouldn't see the resource owner at all if you replaced the plugin. So seems like your server is still using old version or you didn't update the right one.

Cheers.

HansAlbers

Hi Kevin,

You nailed it. I must have made a mistake uploading the .phar to our server. I corrected my mistake. The interface indeed no longer shows that resource owner field, moreover, the whole thing is working perfectly fine now!

Many many thanks for your help and sorry for my stupid mistake causing me to steal your time.

I'm hoping that this will also solve my other issue with the agent alerts, (other thread) which I will tell you about once I know the results of that.

Thanks again and have a great day.

Hans