JDBC Realm: GlassFish v2.1 = OK; GlassFish v3 = fail with invaliduserreason

Posted by Vik Gamov on Stack Overflow See other posts from Stack Overflow or by Vik Gamov
Published on 2010-04-05T10:55:26Z Indexed on 2010/04/05 11:03 UTC
Read the original article Hit count: 466

Filed under:
|
|
|
|

In my J2EE 5 application I have a JDBC Realm based security with Form method. Encrypt method is MD5 as default. The database is PostgreSQL 8.4 installed locally (or 8.3 available via lan).

My app used to work finely on GlassFish v2.1 server with PostgreSQL 8.3, but now I need to deploy it on GlassFish v3. I am absolutely sure I have done all the same config on GFv3 like creating Connection Pool (which pings with no problem), JDBC Resource and JDBC Realm.

But on GFv3 I get login exception with "invaliduserreason" while the database schema is just created from the working database script. I have checked the data and entered login/password thousand times and it seems that data is all right.

So where can I find the reason of unworking security? Please, advice.

NetBeans 6.8 Thanks.

© Stack Overflow or respective owner

Related posts about java

Related posts about j2ee