Not sure if this works for you, but I've set up a standard database realm and use a generic role in web.xml (say, "authorized"). Then, I have a simple action that checks specific roles for sitemap level control of other resources. To give access I assign a user the generic "authorized" role and also any specific roles needed to access the applications protected by the sitemap action (say "admin" or "user" etc.) Did that make any sense?
I can pass on specifics if you're interested. If the action sounds like it has general appeal, I can submit it for inclusion. It's very simple, but has worked well. Geoff Howard > -----Original Message----- > From: Jeff Sexton [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 07, 2003 5:14 PM > To: [EMAIL PROTECTED] > Subject: Realms and Cocoon > > > > I've been able to use > > <security-constraint> > ... > </security-constraint> > <login-config> > ... > </login-config> > > In a $TOMCAT_HOME/webapps/cocoon/WEB-INF/web.xml for a certain Cocoon > application running under Tomcat. However, it seems I can only have a > single <login-config> element in this file. How do others create separate > and different passwords and roles for separate Cocoon applications? > Ideas? > > Thanks > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > > > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
