Deploying a web application (.war) that includes Hbase-0.89.20100924-28 to the Glassfish v3.0.1 server will kill the servers ability to perform web authentication, including the ability to log into the admin.
After starting up the server, with no apps yet deployed, everything works as expected. If a password is set for the administrator (none is by default), the login form is presented and the admin is able to log in. If no admin password is set, no login prompt is presented and the user goes directly to the admin console.
Once my app including Hbase-0.89.20100924-28 is deployed to the server, web authentication becomes impossible for any apps that are using it and for the admin console itself. If no admin password is set, suddenly the login form is shown and the console is inaccessable. The specific error in the glassfish logs is "javax.security.auth.login.LoginException: No LoginModules configured for fileRealm". If the app is trying to use ldap, it's the same error with the ldapRealm. In both cases, it's nonsensical since they are built-in realms with login modules provided and configured by default.
If I undeploy the offending app, the server is still unable to do authentication, throwing the same error. Only after undeploying the app and restarting the server does authentication work.
I encountered this error first on the centos 5.5 system listed and reproduced it on my workstation running Fedora 12. I also verified that the problem does not occur when running the app with HBase 0.90-rc1 (which is what I'm primarily using in development).