|
I got JAAS in JBoss-2.2.2_Tomcat-3.2.2 to work
(thanks to an excellent tutorial on jboss.org!!) and it is works
FLAWLESSLY! However, I then discovered what others have found out:
that the basic "interest" example ejb will not work, because "interest/Interest"
is not bound (I checked in localhost:8082->JndiView->list and
Interest does not exist anywhere). See http://www.mail-archive.com/jboss-user@list.working-dogs.com/msg13087.html
As a result, I'm going to use
JBoss-2.2.1_Tomcat-3.2.1 and Tomcat's JDBCRealm (yes only securing the servlet,
and not using db pooling, and not having a jndi security resource) to do
Authentication&Authorization using a database and wait until the newer JAAS
in in JBoss-2.2.2_Tomcat-3.2.2 is released in a non-beta version of
JBoss.
Q1: Is this a good thought process or am I
way off base?
Q2: Did I ready the JAAS in JBoss-2.2.1
correctly... you can only deploy beans with users.properties and
roles.properties? (e.g. there is no database interface?).
Q3: If going with Tomcat's JDBCRealm is a
good temp solution, how to you restart *just* the JDBCRealm (instead of the
restarting all of JBoss) when I get the message:
2001-06-18 10:28:42 - ContextManager: JDBCRealm:
The database connection is null or was found to be closed. Trying to re-open
it.
Thank you,
Matt Vincent
|
