Ali Sakebi wrote: [...}Just a thought : if you are going through Apache anyway, and are thinking of using mod_perl anyway, can you not do both authentication and authorization in Apache/mod_perl, before you forward to your webapp (I presume under Tomcat) ? mod_jk will forward the user authentication to Tomcat if you ask it nicely. Or rather, it seems that mod_jk will pass it anyway, but Tomcat by default disregards it and does it's own AAA. But you can tell it otherwise :
See this : http://tomcat.apache.org/tomcat-5.5-doc/config/ajp.htmland look for the attribute "tomcatAuthentication" of the <Connector> element.
Note : Apache/mod_jk cannot pass a "role" to Tomcat, because there is no such thing as a "role" really in Apache. But if you create a PerlAuthenHandler, you could add a HTTP header to the request, before passing it to Tomcat, and pick that header up in your webapp (or a servlet filter) under Tomcat. The same for the user-id by the way, so you could remove the AAA part entirely in Tomcat, if that suits your schema.
André --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|