@[deleted] - osTicket does NOT store password as MD5 hashes. The system allows MD5 as fallback (necessary for manual password reset) but it gets rehashed on login. Details on how osTicket hashes passwords can be found in include/class.passwd.php
That's really what I thought. Before I came here I got lots of MD5 functions in Java and all of them returned the same result when applied to my osTicket password stored in the database. But comparing the result with the crypted password stored in the ost_staff table shows that it is different from it. So, I thought that there should be something more.By the way, in which table and column does osTicket store the hash generated for a password? I think now that I need this information to assembly the encrypted password.Is this the way to go? If not, what's the right thing to do? What do you advise me to solve the authentication problem agains the ost_staff table in my application?Marcos