Upgrade to v1.18.2

moliky

I’m currently using osTicket version v1.18 (724de45) and would like to update to v1.18.2.
According to the release notes on GitHub (https://github.com/osTicket/osTicket/releases/tag/v1.18.2), the update includes improvements related to OAuth2:

Show Scopes and Enforce Strict Mode (commits: a77cf53, 390555d)

It appears that only two files have been modified in this release.

My question is:
If I replace these updated files on my server with the new ones from the repository, will the system function properly without issues, or is a full upgrade process recommended?

KevinTheJedi

moliky

Full upgrade always recommended - if you updated those two files you’d still be on the same version. Since you are already on 1.18.x you won’t have to run the any database upgrades. You’ll simply replace the code files and voila you’re up to date. Just make sure you update any installed plugins as well.

Cheers.

moliky

I have updated those 2 files to address the Microsoft email login issue.
However, the problem still persists—when logging in with a Microsoft email, the user is redirected to the main page without proper authentication.

Do you have any suggestions for resolving this issue?
Please note that I have already created a new registered application in Azure and generated a new secret, but the issue remains unresolved.

KevinTheJedi

moliky

First of all, did you read my last message? You need to do the full upgrade process not just update two files. Secondly, after you do that you need to also update the plugin. Lastly, after that try logging in via an incognito/private window.

Cheers.

moliky

Yes, I have completed all the steps, but the issue persists. Should I try removing the email and adding it again?"

KevinTheJedi

moliky

Show screenshots of your app registration and plugin configuration. Also, check your PHP error logs for any related errors. Some people (especially people using windows servers) run into an issue with PHP cURL certificate.

Cheers.

KevinTheJedi

moliky

I just recreated a whole new app registration and new user and everything and I was able to login successfully as a User and Agent. I was also able to authorize a system email. So I do not believe it's an issue with the software/plugin but rather your setup/environment/configurations.

Cheers.

moliky

Thank you for your response. The issue has been resolved. I created a new app registration in Azure, and everything is now working as expected.