G
george63

  • May 10, 2024
  • Joined Jul 28, 2020
  • 0 best answers
  • KevinTheJedi Excuse me, I have this issue too. I'm using osTicket several years already, and it suddenly stopped getting mails yesterday - ticket expired. That happened before, but now, for first time, it wants approval from admin which was not the case until now. If i use my admin account, the plugin gives me that account mismatch error. The fact is that I'm Global Admin and I have delegated myself Edit access to my helpdesk account long time ago for other purposes. The only think I didn't do is the change in step 1. I'm not a programmer, however, and I don't know how to use GitHub and what to do with that pull request. Can somebody tell me how can I patch my OAuth plugin so our help desk can read and send mails again?

    • KevinTheJedi I'm sure there is a default place to check for MySQL on windows. I've installed MySQL because of oSTicket following video instruction on osTicket's web site. I never used MySQL before and I don't need it for anything else. I just want user search in osTicket to work as expected, nothing more. Unfortunately it does not work and none of suggested workarounds in this thread does not work either.

      • I have similar problem, but in my case search works at some places but does not at others.
        Search box in user list - works.
        Search dialog which opens on new ticket creation, change user ticket or add collaborator - does not work.
        Search box in new ticket form which appears on drop-down under select user - works!

        Please, where the SQL logs which some users have posted here come from, so I can look at mine?
        Our version is v1.17, on Windows. I recently upgraded from v1.14. Before the upgrade, search worked everywhere.

        • This is great to point osTicket to get messages from specific subdirectory, but unfortunately it is not possible to use it for two different e-mail settings. For example I would like to have messages from one folder to be used for one set of topics, and the other - for another. For this two different mail configurations has to be made, but login user has to be the same for both. However when one attempts this, osTicket says that login information is already used for another account. It should be designed specifically as a feature, so we can make more input folders for one mail account and specify respective Department and Topic for each folder.

        • I think that there is something different in osTicket between user and agent sections regarding authentication. Because anonymous authentication is disabled in IIS, ever successful loading of https://helpdesk/login.php requires authentication and it is done actually (which can be proven if page is loaded from incognito browser session, where automatic credential submission does not work, so the browser's standard login dialog pops up). However osTicket user portal doesn't honor this authentication and keeps user in "guest mode" until manual authentication is made. Maybe someone more skilled in php could dig into it, and found the reason...

          • Hello. I installed and configured osTicket v1.14.2 on a Windows 2019 server on Microsoft IIS. Here's my version info and plugins:


            I got LDAP authentication working fine against Active Directory for both users and agents. Then I wanted to achieve SSO so users and agents don't have to type their windows passwords if they access the Helpdesk from a domain joined computer. I followed the instructions for "Setting up Kerberos Authentication for a Website in IIS" in this Microsoft tech community article. Since my setup is fairly simple - the machine name / hostname is "helpdesk" and the URL I'm using is https://helpdesk/, so I just enabled Windows authentication and disabled anonymous authentication for osTicket web site in IIS, and it immediately started working for agents. Accessing https://helpdesk/scp automaticaly logins the agents without showing agent login screen. However I'm not able to achieve the same with end user interface. Users are still being asked to provide their user name and password when they access https://helpdesk/ and click "Sign In". Is there a way to avoid this?

            Best regards,
            George