jens_E Yeah, i edited the oauth2.php file with the changes under OAuth2AuthBackend

jens_E I did everything and the plugin is installed but when i try to configure the authentication i get this:

Gian2003k
Are you logged in?
Please look at your php error log. It seems you get a php 500 error. Look at your modified code, if you have a typing error...

jens_E where can i find it?

jerer Thanks a lot. That works for us.

I don't know your System. So I can't say, where you can find this logs.

jens_E I think i will wait till the updated plugin comes out... I literally can't figure out what i'm doing wrong...
For example now i have two identical plugin to install, and one of them gets me the http error 500

Checking in to say the fix worked for me. I used DBeaver as another use above demonstrated to make changes to the (MySQL) database, and it worked great.

Kevin, any updates to when the updated plugin will be released? I'm also having a difficult time making the changes. I have not been successful. For now, i'm working tickets out of the mailbox itself. We would even pay support to update the plugin if possible.

He stated in another thread next release cycle.

jiggs

We actually should have a build of the OAuth2 plugin ready much sooner than that. We are wrapping up the changes for aliases, etc. now and looking at pushing the new build to the website’s download page next week. We don’t allow PHAR uploads on this Forum for security reasons; otherwise I would’ve had a build up this whole time.

Things to keep in mind if it’s not working:

• Make sure the plugin folder and all files are fully extracted. If you’re using Windows switch the quotes around (single to double and vice versa) in the extraction command.
• Check your include/ost-config.php file to make sure you are modifying the correct database.
• As I’ve stated before in this thread there are multiple callback() functions in the plugin’s oauth2.php file so you need to replace the one for the OAuth2EmailAuthBackend backend specifically. Make sure you replace the entire function.
• Make sure the database changes are saved properly by running SELECT queries afterwards.
• Make sure that for each system email you login to osTicket in incognito window and when you are brought to Microsoft you login as the email itself. As stated earlier in this thread aliases, resource emails, and shared mailboxes WILL NOT WORK at this time until the new build is released.
• Make sure you restart the web server and PHP-FPM (if you’re running it) to clear any file cache. PHAR files tend to be aggressively cached.

Cheers.

Our system was functioning until yesterday. I have a ticket open with Microsoft to find out how to resolve the issue.
Do any of these point to a solution?
https://learn.microsoft.com/en-us/entra/identity-platform/scopes-oidc

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/
Transition from API v1.0 to API v2.0

ramrajone

New plugin will be available soon. We have changes made (here and here) but we need to test, etc. before releasing.

For now read above for the temporary fix:

• https://forum.osticket.com/d/105728-ms-oauth2-error-the-api-version-v2-has-been-depreciated/41

Cheers.

ericbrun

Not sure, but someone else had this very same issue earlier in this thread and they found out their certificate expired and needed to be renewed and updated in the email OAuth2 config.

Cheers.

If we are using OSTICKET on a hosting provider i.e Krystal UK how do we apply the changes on the backend, before doing the GUI changes?

martinleggott

You would need to contact your hosting provider as each provider is different. Depends on if they have CPanel, or SSH, etc.

Cheers.

after Doing all steps , after authenticated the email , it return to ostickets home page , not the email configuration page

ramrajone

Whatever order you want. Both simply have to be done before doing changes in the UI.

Cheers.

tamer229
KevinTheJedi please help

tamer229

It sounds like you configured the app registration or plugin incorrectly. Go follow the steps in the documentation to ensure you did everything correctly:

• https://docs.osticket.com/en/latest/OAuth2/Microsoft%20Authorization%20Guide.html

Cheers.

KevinTheJedi
everything was fine till I tried to configure the new plugin and modify the PHP files

tamer229

That doesn’t really help much. Things can change, secrets can expire, etc. I would recommend going over the PHP changes you made to ensure you did them correctly. Then double check your plugin and app registration settings as shown in the docs. If you still have issues I’d recommend configuring a new app registration and reconfiguring the email in osTicket.

Cheers.

I've only had to upload the new th-oauth2.phar and then as soon as i re-apply the token it was successful and started pulling down emails again.?!

martinleggott

I would still make changes to the core codebase but glad it's working for you!

Cheers.

KevinTheJedi
Thank you very much for a quick fix, it works just fine
Very much appreciated

Thanks a million! Our helpdesk is back! Thanks Kevin and team, as well as community!

chris-plahn

Sounds like something is misconfigured within the email configurations or app registration. I would recommend creating a new app registration by following the steps in the documentation, replacing the needed information in the email configurations to match the new app, replace the Scopes with the ones I posted above, and then submit the popup. Keep in mind you should be doing so in an incognito/private window to avoid authorizing the wrong account.

Cheers.

KevinTheJedi Thanks yes I have tried all that as well as deleting and recreating the plugin and email accounts. .

chris-plahn

So you have done ALL of the following and still have issues?

• Downloaded the new build of OAuth2 plugin from the osTicket download page.
• Replaced your existing auth-oauth2.phar file with the new one.
• You’ve made these changes in your code.
• You’ve restarted your web server (and PHP-FPM if you’re running it) to clear any server-side file caching. If using a hosting provider they will likely have additional file caching and if that’s the case reach out to ask how to clear said cache.
• Opened an incognito/private window.
• Navigated to your system email in osTicket.
• Clicked Remote Mailbox and clicked Config.
• Deleted the existing token (if one).
• Clicked IdP Config.
• Replaced the Scopes with offline_access https://outlook.office.com/IMAP.AccessAsUser.All https://outlook.office.com/POP.AccessAsUser.All https://outlook.office.com/SMTP.Send.
• Submitted the popup.
• Logged in as the email you are configuring in osTicket.
• Consented to the permissions.
• Redirected back to the email in osTicket with a success banner.

If so then I’m not sure what’s happening and you would simply need to post everything you have so we can try to help you. I simply cannot replicate this.

Cheers.

KevinTheJedi
Yesterday we ran in this problem, after editing the plugin its working fine.
We're using exchange online usermailbox with 2FA.

Thanks.

jerer hi, i modified the url and create the file j.son, but noew i have this error in authentication cURL error 60: SSL certificate problem: self-signed certificate (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) Can you help me?

f07pd

... simply scroll up and read:

• https://forum.osticket.com/d/105728-ms-oauth2-error-the-api-version-v2-has-been-depreciated/242

… or read here:

• https://forum.osticket.com/d/105871-new-build-of-oauth2-plugin-released

Cheers.

ssalehahmed2

Then you are not doing something right. Please follow the guide here step-by-step:

• https://docs.osticket.com/en/latest/OAuth2/Microsoft%20Authorization%20Guide.html

Once you get to the Outlook Scopes field replace the default value with this: offline_access https://outlook.office.com/IMAP.AccessAsUser.All https://outlook.office.com/POP.AccessAsUser.All https://outlook.office.com/SMTP.Send

Then when you submit the popup and go to microsoft, you login as the email you are configuring in osTicket. Then you consent to the permissions and you should be good. If you have to request consent from an admin this will not work. Your admin will need to consent on behalf of the org in the enterprise applications or allow users to consent themselves.

Cheers.

I recreated the whole email but again same thing. after updating the OAuth2 plugin, I am not getting "resource detail" and "email address attribute" is there something i am missing