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.

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

KevinTheJedi
Thankyou very much the issue was resolved as i was not putting the correct info.

Cheers

Thank very much for instructions provided above at: https://forum.osticket.com/d/105728-ms-oauth2-error-the-api-version-v2-has-been-depreciated/242

They worked perfectly for addressing this issue.

KevinTheJedi

I have tried this for the error
array ( 'code' => 'Gone', 'message' => 'The API version \'V2\' has been deprecated.', )

Update the callback() method, run this caommand inside plugin directory "php -r '$phar = new Phar("auth-oauth2.phar"); $phar->extractTo("./auth-oauth2");" , update the table ost_plugin install_path to plugins/auth-oauth2 and ispher 0.

Still the error persistent. osTicket (v1.18)

Anything else to try please ?

No-U-turn

No longer need to do that. Simply revert the changes you made, download/install the latest plugin, and follow these instructions (if updating an existing email in osTicket follow instructions in the Attention notice at the top).

Cheers.