This could not be more irritating... my
test environment produces expected results and an application that works. In my production I am not getting authentication to work.I am testing authentication by creating a new user and then attempting to log them in with the correct credentials.
what happens?
I get nothing but the login error page defined in web.xml indicating that the authentication failed. I get nothing in my logs and not even a bubbled exception.
how is my realm configured?
with the following context.xml:
All urls,databases and ttable names are correct as have been checked MANY times.
What do I think could be wrong?
not a
tomcat bug but my hosting providers (eapps.com) configuration of tomcat. Of course it is difficult to gwt them to buy it but here is why I think this...
Originally, I wanted hibernate to use a <resource> defined datasource in server.xml global resources and this failed.There was a workaround because hibernate can manage it's own pool but with authentication there is none as this is pure container with no plugins to do this. In short , I do not think tomcat is finding any <resources> in server.xml or context.xml Does anyone have a clue as to what is going on?
some more info production an test containers are same version , same
jdbc lib jar, exact same database names, table names, column names and user names to narrow down possibilities of errors.