As far as I know, the users, roles, and user_roles tables are global and
will get used by whatever Web applications you have protected. Are you
saying that you want to have a separate set of these table, one for each Web
application? Why not just create different roles, one for each Web
application?
Personally, I'm hoping that the MemoryRealm class will be improved upon in
the future. Putting this information in a SQL database seems like a lot of
overhead to me (even though it does seem to work well, once you get it
setup). Basically, the functionality that I'm looking for in MemoryRealm is
the ability to tell Tomcat to reload the user database. Also, it would be
nice to have a "digest" property like you have with JDBCRealm, so that you
can store the passwords as hashes instead of in clear-text.
Jon
----- Original Message -----
From: "Nitin Goyal" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 23, 2001 6:46 AM
Subject: JDBCRealm Security setup Help Required.
> Hi,
>
> We are setting up the JDBCRealm security with Tomcat. We have seen the
> jdbcrealm.howto file and we are able to make a small test sample run
perfectly
> fine. However, there are some clarifications in the implementation
scenario
> that require your inputs:
>
> We have more than one webapps running in the Tomcat Server. I understand
that
> it is recommended to create a separate schema for jdbcrealm
authentication, but
> one can create the authentication schema in the application database too
rather
> then create a new schema. Lets say we have 5 database schemas in a single
> database, which are for 5 different webapps, and we want to use JDBCrealm
> authentication. One option is to create a separate schema (as mentioned
in the
> .howto document), but this will require extensive changes in our code for
each
> web app. In case we are to bundle the security schema with the
application
> database schema, how do we create the corresponding multiple
RequestInterceptor
> entries in server.xml for all of these? How will tomcat validate the
username
> with the correct username/password? Are there any other ways to implement
this
> authentication? Are there any disadvantages in NOT creating a separate
database
> schema?
>
> Any suggestions are most welcome!
>
> Regards
> Nitin Goyal
> Webrizon eSolutions Pvt. Ltd., INDIA
> [EMAIL PROTECTED]
> There is no failure except in no longer trying.
>
>
>
>
