Closed bastienho closed 8 years ago
The second error implies that the matching agent account cannot be found. This usually means that the CAS username and the osTicket username don't match up perfectly. You have two options:
Thank you
But it worked until OsTicket 1.8, and it still work for end users
Hmm, something else is going on. I'll try to reproduce this later tonight.
However, this is a different issue than those two linked bugs. In this case your agents are fail authentication.
I wasn't able to reproduce this locally on latest commit in develop-next. Have any other settings changed in your environment? Are you using the latest version of the plugin?
Hi, Sorry, after almost an entire day trying to make it work, I finally have a good result on the evening.
And I don't know exactly what happened.
First, I had both front and back broken with CAS, just getting a 404 when calling the api
And after a server (Nginx) reconfiguration, it fell in work.
Thank you for your work.
Hi
it seems that the bug solved in #5 and mentioned in #8 still occurs, even on develop-next
The first time
other times