KevinTheJedi effectively, I have removed web.config and regenerate it automatically with iis otherelse the site doesn't works (ERROR 500). It is probably the cause.
So I will try to use the web.config provided by default.

      Tfrere Kevin, well done!
      I have restored the web.config and select the php version in php manager (iis).
      Now I have an another error (curl error 60: SSL certificate problem)

      But it s an another error, I will investigate before asking a lot of questions!

      Tks for your availability and your perfect advices!

      Cheers,

      Tfrere

          Tfrere

          There are other threads on the certificate error but in short you need to download the official cURL certificate and configure your PHP instance to use this. You can look online to see exactly how to do this, it’s very simple luckily.

          Cheers.

            Tfrere

            I forgot to ask, is there anything special you need to do to load the web.config on IIS? If so, please post instructions if you would be so kind so that others can see how to resolve this. A few people on the Forum have ran into this and some still can’t figure it out.

            Cheers.

                KevinTheJedi Dear Kevin,
                To resume:
                To upgrade to osticket 1.17:

                • download php 8
                  -download osticket 1.16 with plug-ins that you are using.
                  -copy osticket 1.16 "upload " folder(don t forget to copy also the recently downloaded phar files in include/plugins folder!!!! otherelse you will receive error 500)
                • go to iis php manager of the osticket site and register the new php folder (8 phpcgi.exe)
                  -upgrade to 1.16 via the wizard on your osticket website.

                Do the same to upgrade to 1.17.
                Finally to configure Oauth2 please follow the documentation available on osticket site.

                My issue, was because in the beginning I didn't copy the phar files. So I got error 500. To avoid this error I have removed the web.config on the osticket folder then I went to php manager and it regenerate the web.config. so the url rewritting indicated in the initial web.config from upload folder wasn't present.

                To resume: copy the entire "upload" folder and the new phar files. Go to php manager to register the new php version and apply the upgrade. That s it.

                For the error 60, I have followed those instructions:

                https://medium.com/@narendravaghela/how-to-fix-curl-error-60-ssl-certificate-problem-80e7dafafa57

                Now all is working perfectly!

                Thanks a lot for your support.

                Cheers,

                Tfrere

                  ADRD I had the same issue with the pop up.
                  I finally restore my database with a backup that I made before installing the plug-in.

                  Br,

                  Tfrere

                  • ADRD replied to this.

                      Tfrere

                      Thanks, I restored a previous version, reinstalled the plugin and it's working better.

                      @KevinTheJedi The URL rewriting enabling seems to have done the trick too.

                      I'm still having failed authentication but that's more likely a configuration issue on my side.

                        4 months later

                        @KevinTheJedi We are getting mime emails sent back to us, OAuth2 does not seem to be working. it is fine for remote mailbox but not outgoing. our configurations are correct as we have followed the guide by osTicket. When trying to enable the status we keep on getting errors.

                          Eyeyo

                          If you have OAuth2 configured for the Remote Mailbox tab then simply set SMTP's Authentication to "Same as Remote Mailbox".

                          Also, make sure when you get a token you get it as the email itself, no other account.

                          Cheers.

                              Eyeyo

                              Well MS is saying authentication was unsuccessful so something’s not right. Again, are you absolutely sure when you were redirected to MS you logged in and consented as the system email you are configuring in osTicket?

                              Cheers.

                                  Eyeyo

                                  Then it doesn’t make much sense. Are you using v1.17.2 and the latest build of the OAuth2 plugin?

                                  Cheers.

                                    Write a Reply...