bimaljr

Our code for this is internal only right now. We will release a test build soon. Please stay tuned.

Cheers.

      2 months later

      KevinTheJedi Has there been any update on this? Our Org has made some changes and if its not supported soon I'm afraid we are going to have to drop OSTicket....

        @danielccross

        The update is we hope to have it released by the end of May. We are currently wrapping up the OAuth2.0 side of things then once complete we are connecting it to the new mail backend and doing some final testing.

        Cheers.

          a month later

          KevinTheJedi Hate to pester again but I'm geting pressure from higher ups has a specific date been decided for the release that will have the support for Oauth2.0?

          Thanks.

              7 days later

              KevinTheJedi Sorry to pester again the reason I ask is our organization has decided to push the requirement sooner than microsoft has. Is there a specific month the release is planned for?

                Add our voice to the throng. We're very excited to get this into production, but the modern auth/Oauth2 is a hard requirement for us.

                7 days later

                Hello, any updates on this?
                I cannot receive any new tickets for 2 days now!

                Is there a plugin we can use in the interim for 365 and/or Google Auth?

                greg2000

                Yes, we are hoping to have v1.17-rc1 released within the next few weeks. Stay tuned!

                Cheers.

                  Tinnitus

                  Looking like next week or the week after. People don’t realize how big of a change this is. We are literally changing the basis of the software.

                  Cheers.

                      KevinTheJedi Definitely a huge change. While the push back sucks, I appreciate you being responsive on the forum and keeping us as up to date as you are able to. Will be waiting for the update and thank you for supporting this huge change!

                          RevAdmin

                          We really appreciate the kind words. It’s been the biggest struggle to get this working. We had to change the entire plugin architecture, create a new OAuth plugin, ditch the old PHP pear libraries, setup a new library (laminas-mail), and change the entire basis of the software (everything email). Excuse my language but PHP really fucked developers by not supporting OAuth via native imap functions, etc.

                          Cheers.

                            10 days later

                            "Small" Rant:
                            As difficult and time consuming this was, it was actually quite a fun and informative project; we’ve really learned a lot along the way and even improved areas of the code along the way.

                            This is also kind of a good thing as some environments don’t have access to the PHP imap extension. Using laminas-mail removes the need for this extension completely. This opens the use of osTicket to more and more environments. For example people using the new macs with M1 chips can’t run x86 based architecture natively; you would have to use an emulator which is absolutely horrible in performance. So this means you basically have to switch to aarch64 based architecture for example CentOS Stream 9 (aarch64). This build of CentOS doesn’t have access to the PHP imap extension so you can’t fetch emails at all. Testing mail fetching in this environment is virtually impossible with the current state of osTicket as it depends on the native PHP imap functions.

                            Obviously v2.0 will be a much bigger leap in terms of compatibility and introduce innovations and performance improvements in virtually all areas of the software. Backend-wise using the new Laravel framework with a complete and optimized ORM is a god send, enabling endless possibilities. Legacy osTicket relies on a completely custom ORM developed by a former employee. It is not complete nor optimized and doesn’t provide a full range of features. Front-end wise using ReactJS and SemanticUI brings a completely new experience and really provides a fully modern UI/UX. We no longer rely on old (sometimes outdated) libraries so we can utilize all the latest and greatest features to be responsive and intuitive across all devices (even mobile). We can’t wait to publish a visual preview for the community in the near future. We are extremely proud of it so far!