I tried with plugin version 0.3 and the redirect url does not work. it just redirects to the homepage when authenticating.
Version 0.5 does not open configuration, just a blank popup.
Any here with a working version?

    sander4000
    Check the network traffic with the developer tools (usually "F12"). Sometimes it shows you the error as soon as you got redirected.

      KevinTheJedi yes, all configuration are correct... in a fresh ost (without data) works perfectly... I made a pre version upgrade (1.14 - 1.16) and from 1.16 to 1.17 and the OST with data works.. thanks a lot for the help

        Is the scope of what is being worked on just generating the token? Is fetching and sending mail also implemented?

          leonlongoria

          Of course. We completely changed the package for mail from PEAR to Laminas-Mail which supports Modern Auth.

          Cheers.

            I must be missing something. I'm on 1.17rc4 and this is what I'm seeing:

              leonlongoria

              fyi for this issue, our organization was doing something weird with our firewall and SSL certs. After going around that everything worked. thanks

                MontanaMac

                You have cURL issues on your server. Please follow the link displayed in the error to review the possible resolutions. this is outside the scope of osTicket software.

                Cheers.

                  margol

                  I have no idea why; I am unable to replicate this..

                  Are you using a test application? Are you sure you set the token expiration to a long period of time?

                  Cheers.

                      update: so the curl error was because of having "organizations" in the urls, changed them to "common" and now it appears to do nothing when saving the config, it just dumps me back to the login screen of the ticket system.

                        MontanaMac

                        Then that most likely needs you don’t have URL Rewriting enabled on your web server. Or maybe wrong endpoints. You need to go to app reg, click the app, click Overview, and click endpoints. You need to use the first two URLs (Authorization v2 and Token v2).

                        Cheers.

                          KevinTheJedi

                          Hi,
                          We have a test app on 17 RC4
                          I didn't change token expiration yet, but today morning I noticed:

                          • mails from Inbox didn't fetch
                          • one of ticket had a time of 'last Update' about 02 AM
                          • token are valid IMAP and SMTP

                          So I made:

                          • go to AOuth2 MS Remote Mailbox, IdP config and click on 'Submit'
                          • and that same Remote Mailbox disable 'Email Fetching' and click 'Save Changes', next enable 'Email Fetching' and click 'Save Changes'

                          After that mails fetch from Inbox.

                          Conclusion,

                          • why mails won't fetch byt one of ticket was update
                          • witch my actions cause fetch emails from Inbox

                              margol

                              Sounds like you need a cron job to automatically poll emails. Then each time it fetches it will update the tokens.

                              Cheers.

                                  6 days later

                                  KevinTheJedi

                                  Thanks for your suggestions!
                                  The last bit of my puzzle was about fetching messages, which simply needed to be scheduled by a Cron job.
                                  Running "RC4"

                                    KevinTheJedi

                                    I made a cron job, before a problems with fetch. Anyway problems gone 🙂 but I still I don't know what cause resolve problem.

                                      I've got all 3 of my installations updated and working fine following the guides however when the ticket is created for or by a Gmail user the replies are being blocked.

                                      Our system has detected that this message is not
                                      RFC 550-5.7.1 5322 compliant: duplicate headers. To reduce the amount of
                                      spam sent 550-5.7.1 to Gmail, this message has been blocked. Please review
                                      550 5.7.1 RFC 5322 specifications for more information.

                                      Any ideas whats wrong?

                                      Thank you

                                        thisiskode

                                        I've found the issue... Outgoing settings were disabled, the old port setting was 25. Changed to 587 and enabled. All is good.

                                        [insert comical abuse here]

                                          Can someone please help me to setup Oauth2. I can't figure out what am I doing wrong.

                                          This is my setup:




                                          After I request the approval, it sends me back to osTicket log in page. Request is approved by admin, but nothing changes in osTicket.

                                          I get this error and if I try to submit again it is still asking to request approval for the same things that are already approved.

                                          Any ideas what should I check or if I am missing something?