sushpep

You are correct in that osTicket does not yet support OAuth2.0 authentication. We have been working on it and actually dedicating time to solely that so that we can hopefully have it released (at least a release candidate) by the Google cutoff date of May 30th, 2022.

With that being said you can disable Modern Authentication until the support is released. In your case maybe you have 2FA enabled and in that case you will need to create an App Password and use that. Please refer to MS docs for more information on App Passwords. If all else fails you can look at the previous posts where people explain what they’ve done to solve the issue or contact MS support for further assistance.

Cheers.

    Hi Sir Kevin,

    Thank you so much for the confirmation. Will do a little bit of further research on this.

    We're currently in the process of migrating from google to office so at this point I wasn't really sure what we could do.

    Many thanks as well for the rough timeline. I did see you noting how much work was needed into reworking the code to get it working. Much appreciation to you and the team for your efforts!

    Thank you!

    Is OSTicket 1.15 currently working with Office365 email accounts?
    I use 1.15.x with O365 currently.
    You have to enable IMAP on the account, and disable 2FA

      Thank you so much! Will give this a go!

      ntozier

      Do I need something else for this? I have already tried this but am still encountering the error. Thank you!

      Below image shows:

      1. Microsoft Office 365 Mailbox allowing IMAP
      2. MFA off
      3. OSTicket Setup with Error.

      https://imgur.com/EDB8TyP

        You are using the same setting that I am.
        Have you tried logging in using another email client using those settings and account details?

          ntozier
          Thank you for the reply. Yes, we have. IMAP does work, tested with Thunderbird. Thunderbird / the server however, only allows connection when OAUTH2 is selected. Normal authentication does not work. Seems to me like it is something on the Microsoft side not allowing the normal authentication method to work despite already being set.

          Maybe because this is a newly created Microsoft account?

            @sushpep

            Probably yes. They released a statement last year or so that new accounts will be forced to use OAuth. Only existing accounts can use Basic Authentication. You may need to reach out to MS support.

            Cheers.

            2 months later

            If anyone is interested.
            Since I have the same problem (BasicAuth disabled in my tennant, osTicket 1.10), I wrote a litte O365 pipe-Gateway that will read the incoming emails via GraphAPI (App-Credential!) and pipe it into osTicket remotely (api/tickets.email). Works like a charme.
            Currently in C# , but should be adoptable to any lang without real problems.
            I'll publish it on my Github the next days, after production tests

              18 days later
              3 months later

              Dear all,
              we are facing this problem as well now and currently working with Modern Authentication Switched off.
              MS has stated that they are depreciating this from Oct 22.
              Has a version of OS Ticket already been released with this support ????

              • RBGE replied to this.

                macsoluk Yes - v1.17 with the OAuth2 plugin supports MS 365's current security setup.

                  I finally got Oauth working but now can’t get fetching to work from the authenticated mailbox

                    Write a Reply...