KevinTheJedi

Fantastic work, as always!
It's great to see such a community-driven open source project, which is benefitting so many of us.
But your statements about v2.0 are a tease 😉 ... Looking forward to seeing it when it comes out!
Cheers for all your hard work, keeping our ticket systems stable. The only downside is that while osTicket is working, it means we also have to work 🙁 lol.

KevinTheJedi Honestly this sounds like although this was a headache for the dev team, the capabilities for email will be much greater moving forward after this huge change. Like I said previously, thank you for your in depth info into this project and all of your work on this. You guys are a prime example of the open source community and represent all of us well. Thank you.

17 days later

Is there an ETA for anything related to this issue? Has anyone running this on Gmail found a solution after 5/31/22?
We have a hard deadline of 10/1/22 and we need to find a solution soon or move out of osTicket.
Would love to stay, but I don't see anything in the new releases addressing this. Please tell me I'm wrong!
Thank you

    12 days later

    alexbuckland

    This coming week. Had issues and people were not available last week so wasn’t released.

    If anyone wants further updates please follow the GitHub repo and you’ll be notified upon a release.

    Cheers.

    Not a long term fix, but I am forwarding my mailbox that needs collection from osticket to a ÂŁ1/month mailbox from fasthosts - then I can pop3 collect all I want - works great :-)

      alexbuckland

      It will eventually be phased out by most if not all major providers but that deadline is way farther away than IMAP/POP3.

      Cheers.

      Hello Everyone,

      We now have the v1.17-rc1 available for download on our website! Please download, install in a test environment, and test away! If you experience any issues please open a new Issue Report detailing the issue.

      A big thank you to everyone for their patience and support!

      Cheers.

        I would like to mention that we need help testing email authorization for MS accounts specifically. We’ve tested email authorization for Gmail (IMAP/SMTP) as well as OAuth2 agent/user authentication for Google and MS. We also need help testing POP for both Gmail and MS.

        Cheers.

        I manage to upgrade my production environment from 1.16.3 to 1.17 RC1 without any hiccups. Manage to activate the OAuth2 plugin and here's where I cannot proceed further. I'm on Office365/AzureAD.

        In Manage -> Plugins -> Oauth2 Client, there's an Instance tab. Do I need to manually create a new Instance? Some fields were populated automatically and I'm not sure what should I modify.

        Then in Emails -> Email Addresses (select primary) -> Remote Mailbox, there's another "Config" tab next to "Authentication" after I selected "OAuth2 - Microsoft". The fields here are similar to the ones in Plugins.

        Do you have a guide on how to get OAuth2 working? I have completed App registration in Azure AD, however Osticket does not show specific error message other than "Configure Authentication".

          danielyee

          You need to go to osTicket, click Config next to Authentication in the email, copy your Redirect URI, go to Azure, register an app, paste your Redirect URI, create a client secret, copy the client id and client secret, go to osTicket, paste your client ID, paste your client secret, and Save Changes. This will then redirect you to Azure to authenticate and accept the scopes.

          Cheers.

            KevinTheJedi
            Hi Kevin,
            I am facing the same issue.
            I've configure the OAuth2-Microsoft and it is save successfully.
            But when I enabling the email fetching option and try to save the setting it'll show me the Configure Authentication error.
            Please find the screen shot.
            first Screen Shot - I've configure the OAuth2-Microsoft.
            Second Screen shot - My OAuth Config parameters.
            Third Screen shot - I'm trying to enable the Email Fetching but getting the Configure Authentication Error.



              korali

              Okay so don’t use the /common/ urls for Authorization and Token Endpoints. Instead go to the Enterprise Applications in Azure, click Endpoints at the top, and use the v2.0 Authorization and Token URLs with /tenant-id/oauth2/v2.0/ instead of /common/oauth2/v2.0/. Then for Resource Details Endpoint instead of /api/v1.0/me use /api/v2.0/me. And lastly for scopes replace profile,email with https://graph.microsoft.com/.default.

              If that doesn’t work then you might need the new build of the plugin and the new patches coming on Monday with RC2. Stay tuned!

              Cheers.