On 19/7/09 18:52, Bill Davidson wrote:
Mark Thomas wrote:
>Alternatively, you could use a database view to present the two sets of
>users as a single table.
What about duplicated user names between the two sides?
That might not be an issue if admin users don't use the public site, and
vice versa. Be better to avoid that if possible though.
Can you reassign admin user names?
There's also the need to make sure that the admin side servlets are
not accessible to the public side and vice versa and that the public
side servlets are accessible without authentication but the admin
side servlets are not.
Container auth uses configurable roles to set authorization, which would
handle this eventuality. Just set up two different security-constraint's.
p
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
