On Wed, 2011-12-21 at 12:39 -0800, Jerry Malcolm wrote: > About a month ago, I upgraded two different servers from TC 5 to TC 7. The > migration went cleanly, and everything has been working fine with the > exception of one thing. About 50% of the time, when I log in to the realm > for my web app (form-based login), the login will fail. When I try again > with the same id/pw it works. I can then log out and log back in > repeatedly with no problem. But if I come back later and try to log on > again, same things. Fails once, and then passes. > > My authentication configuration hasn't changed for years on these webapps, > and this has worked solid on TC 5. My database (MySQL) hasn't changed, and > the user tables are unchanged. The only thing that has changed is TC 5- > -->TC 7. And the problem has hit both servers, completely independent of > each other, other than they both got the TC 7 upgrade. > > First of all, has anyone ever heard of this situation? Second, any idea > how where/how to turn on detailed tracing/logging of the authentication > calls to see what might be going on in the authentication code in TC?
My first thought would be to capture the HTTP traffic from a good and bad request and compare the two. Before digging in further, I'd want to make sure that both requests were identical. Since, if the requests are not the same, that could certainly account for the difference in behavior. Wireshark is helpful for capturing and analyzing the packets. Dan > The > only information I'm getting is that the id/pw were not correct. But > again, same id/pw becomes correct when I submit it a 2nd time. > > The one thing I didn't change was the MySQL connector. Should that have > been changed for TC 7? (Just guessing now) > > Suggestions for how to proceed? > > Thx. > > Jerry
