T
tonydew

  • Nov 30, 2024
  • Joined Dec 4, 2023
  • 0 best answers
  • In Understanding %{recipient.ticket_link}

    Oh! It makes so much sense when you know what is going on.
    Thank you

  • In Understanding %{recipient.ticket_link}
    • osTicket Version: v1.18.1 (0375576)
    • Web Server Software: Apache
    • MySQL Version: 5.7.44
    • PHP Version: 8.2.25

    I'm having issues getting different results for a reason that I cannot figure out when I use %{recipient.ticket_link} in an email template (Ticket End-User Email Templates/Response/Reply Template).

    Sometimes, %{recipient.ticket_link} generates a link with an auth code. Other times, it generates a link to the ticket by its ID.

    If the email generates the following, with an "auth={code}" query string, they will go straight to the ticket in question.

    If the email generates the following, with an "id=####" query string, the get caught at the email and ticket id login.

    I cannot for the life of me figure out why sometimes you get one vs the other. What I am hoping for it the "auth" link every time.

    • KevinTheJedi replied to this.

    • tonydew

      Auth codes are only available when there are no collaborators. If there are collaborators then auth codes are not added as it’s a single email going to the user and CCs. Since it’s a single email it’s a single auth code which means the collabs could then masquerade as the user and that’s not good for many reasons.

      Cheers.

      • In Suddenly cannot log in by OAuth2 in 1.18.1?

        KevinTheJedi

        Damn... I figured the same thing but couldn't find it. Everything I found was valid. Then I looked at the same application but the "App Registration" view and there it was...

        Thanks for t he nudge in the correct direction.

          • In Suddenly cannot log in by OAuth2 in 1.18.1?

            We've had a functioning OS Ticket 1.18.1 install running for months using the OAuth2 plugin with M365. It was a little bit tricky to setup at first, but has been rock solid since.

            Sometime this week, logging in via M365 stopped working. You click the (in our case) "Sign in with Microsoft 365" button, it goes through the M365 sign in process, then redirects back to the home page. Doesn't matter if you try to log in as a user, or an agent, you end up back at the home page, and not logged in.

            It doesn't matter if you clear cookies, change browsers, even different browsers on different devices. All just revert back to the home page now, without having logged in.

            From what I can see, nothing changed on the OsTicket install on the server, or with the Entra integration.

            Any idea what might be happening?

              • In Potential plugin sanity / feasibility check

                KevinTheJedi Thank you for the detailed reply. I have no intentions of promoting a third party plugin. Just scratching an itch in our own usage of osTicket. If I am able to create a plugin I would of course have the code available on GitHub, but wouldn't abuse the osTicket forums with advertising / promoting it etc.

                Also, I understand that 2.0 is on the way and I've heard suggestions that the functionality I am after may be part of it. I'm happy to the core application work out of the box if so! There would be no hard feelings about time spent on an old codebase plugin.

                • In Potential plugin sanity / feasibility check

                  I'm considering creating a plugin to add some functionality that I don't believe exists already in osTicket. I'd like to be able to automatically create a task on a ticket if it is transferred from a specific department, to any number of other departments.

                  Before I dive in a learn how to create plugins for osTicket, I have two questions:

                  1. Am I correct in that this functionality does not already exist in osTicket?
                  2. If it doesn't exist, are the required Signals available in the plugin API to do what I am looking for?

                  For example,

                  • watch for ticket modification
                  • check if it was transferred from "Department X" to wherever.
                  • if so, create a task attached to that ticket
                  • KevinTheJedi replied to this.

                  • tonydew

                    1. This does exist it’s just not automatic. An Agent would have to manually create a Task on the Ticket before/after Transferring the Ticket.
                    2. Yes, look at the transfer() method for Ticket and you’ll see logEvent() that sends signals for certain actions. Both the core and plugin codebases are fully open source and available on GitHub.

                    I will note that we are not accepting any new plugins or features to the current (legacy) osTicket codebases as we are focusing on v2.0 (full codebase rewrite). It’d be highly advisable to clone the osTicket/osTicket-plugins repo and add your plugin within your own fork so you can easily maintain and track issues within your own repo. Just to note, you can't use this forum to advertise nor to report/track issues with your 3rd party mod.

                    With all this being said, the legacy codebase will only be around for so much longer (another year or so). The plugin architecture/landscape will be changing dramatically in v2.0 so all existing 3rd party plugins will be virtually obsolete on release.

                    Cheers.