KevinTheJedi
my dear thanks for your keep nagging for my issue , but because i have to deliver a working Ticketing system to my Management , everything works fine so far but only the mail fetching still not operational .

i already have the 1.17 release installed

    atahaynah

    You are using RC4 which has bugs and is not the "stable" release of v1.17. You will need to follow my instructions in my previous post.

    Cheers.

    a month later

    KevinTheJedi

    Hi Kevin,

    I'm having a similar issue with this. I am getting /api/auth/oauth2 rather than /api/http.php/auth/ when clicking "Sign in with Azure"

    I've followed the wiki guide for setting up oauth for agent login & gone through this thread and others to try and make sure I haven't made a mistake anywhere.

    The web server is apache with rewrite enabled. I've tested that rewrite does work by temporarily adding a different rule to the .htaccess in the api folder. The rule was a rewrite from api/foobar/ to www.example.com & that did trigger.

    Azure is showing the log in attempts as successes.

    Thanks for any help or guidance you may be able to provide.

      Lister

      You'll have to create your own thread with detailed info, screenshots, and steps. /api/auth/oauth2 is the correct URL.

      Cheers.

      a month later

      I got the token right now.

      But when i click enable and save changes for outgoing mail it says this

      So when i test outgoing mail it says the test was successful but it wasnt

      Where can I see my logs or how do I troubleshoot whats going on if im using centos with cpanel

        ricardogomez

        You’ll need to contact your hosting provider. It’s likely they have restrictions on outgoing SMTP connections or a firewall, etc.

        Cheers.

        18 days later

        KevinTheJedi

        Cheers,
        I am having a problem with OAuth2 that i can´t understand...
        Can you help me please?
        The error is
        AADSTS9002325: Proof Key for Code Exchange is required for cross-origin authorization code redemption.

        What am i doing wrong?

          KevinTheJedi

          I have eliminated the app registration in O365, then created a new one and sucess.
          SMTP continues to get an error : 535: 5.7.3 Authentication unsuccessful i will continue trying...
          Thanks Kevin

          I've been working with my org's IT dept to add oauth for our osTicket instance and got this "AADSTS9002325: Proof Key for Code Exchange is required for cross-origin authorization code redemption." error today as well.

          Were you ableto find a cause? We tried making a new app registration as well.

          One thing I was curious about, in the guide it says "Here it is very important to login to the email you are trying to configure in the helpdesk. Once logged in as the system email you are trying to configure, you can opt to Consent on behalf of your organization, and then click Accept."

          in our case the account login is different than the email address for this account, does the quoted documentation mean that will cause a problem?

            rhuggins

            With the current iteration of the software and plugin yes it will cause an issue. We have patches coming that will allow you to use a global admin or service user to authenticate and consent but currently you must sign in using the email itself.

            Cheers.

              Thank you very much. I'll try changing the email address to match the login name.

              a month later

              agrservice

              Please do a recursive search before posting. You don’t have URL rewriting enabled.

              Cheers.

              a month later

              KevinTheJedi The system doesn't allow me to log in with system email? Where should I enable this setting? We are using a regular mailbox for receiving and sending emails. In order to configure Oauth, I need to log in to OsTicket with that same user however I am getting access denied error.

                valdoltra Nevermind. I just gave myself a high five... to my forehead.... with a chair 🙂

                I got O365 cached signin so it always tried to log in with my username. Once I logged in with my helpdesk account and remained signed in it worked.

                I'll take my Darwin award now thank you

                Write a Reply...