Could there be a conflict between some older tomcat jar and the glassfish stuff? Maybe something is getting picked up somewhere gumming up the works so the glassfish setting is getting clobbered with a setting from tomcat? My old tomcat files are still on the disk but tomcat is not actually installed anymore - its just a copy from a backup drive.
This is what the realm part looks like in my domain.xml:
<auth-realm classname="com.sun.enterprise.security.auth.realm.jdbc.JDBCRealm" name="jdbcrealmwonderland">
119 <property name="jaas-context" value="jdbcRealm" />
120 <property name="datasource-jndi" value="jdbcrealmwonderland" />
121 <property name="user-table" value="webdev.wonderland_users" />
122 <property name="user-name-column" value="username" />
123 <property name="password-column" value="pword" />
124 <property name="group-table" value="webdev.wonderland_roles" />
125 <property name="group-name-column" value="rolename" />
126 <property name="digest-algorithm" value="MD5" />
127 <property name="encoding" value="Hex" />
128 </auth-realm>
I tried it without Hex and without MD5 and had no luck.
[Message sent by forum member 'cal41' (calgach_at_yahoo.ca)]
http://forums.java.net/jive/thread.jspa?messageID=381116