You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Bojan Smojver <bo...@binarix.com> on 2001/09/26 02:34:42 UTC
TC 3.3 + mod_jk + j_security_check
Unless this is now implemented automatically in mod_jk, I think it would
be worth mentioning in mod_jk HOWTO about the need to JKMount
j_security_check when form authentication is used in applications.
I think I should be able to fake a paragraph about it (with examples).
Bojan
Re: Tomcat 4.0 RPMs?
Posted by Christopher Cain <cc...@mhsoftware.com>.
Hi Vic. We're currently trying to sort out the best way of packaging a 4.0 RPM.
TC4 has quite a few external jar dependencies ... some optional, some
mandatory. We're kind of between a rock and a hard place with both a few of the
RPM packaging policies as well as some jar redistribution issues.
The prevailing theory seems to be that the RPM should include just the absolute
minimum number of jars required to successfully run a minimal build of Tomcat.
The rest will still have to be downloaded separately (although we might make
a "tomcat-supplimental.tar.gz" available containing all of the optional jars
that we can safely redistribute). The problem is that RPM packaging policies
frown upon including external binaries (in our case non-TC jars) in the RPM,
and beyond that, doing so is not really good form anyway.
In other words, the RPM install isn't going to be as painless as we would like.
If you are comfortable with building from source, and if you need anything
other than a minimal build, the source might be your best bet. (You could also
just download the binaries, of course.) I'm not even sure that an exact
approach for TC4 RPMs has been decided upon, and I'm also not sure what Henri's
(our RPM packager) timeframe is, so AFAIK the date on having an RPM is still up
in the air.
Quoting Vic Ricker <vi...@sheetz.com>:
> Hi.
>
> Will RPMs for Tomcat 4.0 be released on the web site any time soon?
>
> I have no problem installing from the tar but I'd prefer the RPM since
> that's
> how I installed the previous version.
>
> Thanks,
> -Vic
- Christopher
/**
* Pleurez, pleurez, mes yeux, et fondez vous en eau!
* La moitié de ma vie a mis l'autre au tombeau.
* ---Corneille
*/
Tomcat 4.0 RPMs?
Posted by Vic Ricker <vi...@sheetz.com>.
Hi.
Will RPMs for Tomcat 4.0 be released on the web site any time soon?
I have no problem installing from the tar but I'd prefer the RPM since that's
how I installed the previous version.
Thanks,
-Vic
Re: TC 3.3 + mod_jk + j_security_check
Posted by cm...@yahoo.com.
On Thu, 27 Sep 2001, Bojan Smojver wrote:
> I was referring to the manual configuration, rather then ApacheConfig
> one. Some people (me :-) prefer to do things manually.
>
> I actually tried with /*.jsp (or /*.vm in my case) only and it (still)
> doesn't work (which makes sense and I don't consider it a problem)
> unless you specify:
>
> JkMount /login/j_security_check ajp13
>
> or whichever other place j_security_check is under. That's what I wanted
> to mention in the mod_jk HOWTO. It might save someone considerable
> amount of time.
+1
Manual configuration is the best :-)
( but ApacheConfig is getting very close )
Costin
Re: TC 3.3 + mod_jk + j_security_check
Posted by Bojan Smojver <bo...@binarix.com>.
I was referring to the manual configuration, rather then ApacheConfig
one. Some people (me :-) prefer to do things manually.
I actually tried with /*.jsp (or /*.vm in my case) only and it (still)
doesn't work (which makes sense and I don't consider it a problem)
unless you specify:
JkMount /login/j_security_check ajp13
or whichever other place j_security_check is under. That's what I wanted
to mention in the mod_jk HOWTO. It might save someone considerable
amount of time.
Bojan
Bill Barker wrote:
>
> If the web.xml contains no servlet-mappings, then forwardAll="false" will
> generate:
> JkMount /myapp/servlet/* ajp13
> JkMount /myapp/*.jsp ajp13
>
> and if in addition, the context uses form authorization:
> JkMount /myapp/path/to/j_security_check ajp13
>
> You need to set noRoot="false" if you want the ROOT context mappings
> generated as well.
>
> Larry has added other options to allow you to specify the directories where
> various files go (e.g. mod_jk.so), but I don't remember them off the top of
> my head.
> ----- Original Message -----
> From: "Bojan Smojver" <bo...@binarix.com>
> To: <to...@jakarta.apache.org>
> Sent: Tuesday, September 25, 2001 7:51 PM
> Subject: Re: TC 3.3 + mod_jk + j_security_check
>
> > What if the only mapping is for instance:
> >
> > JkMount /*.jsp ajp13
> >
> > Will it still work?
> >
> > Bojan
> >
> > Bill Barker wrote:
> > >
> > > This is now implemented automatically in the ApacheConfig module. By
> > > default it does:
> > > JkMount /myapp/* ajp13
> > >
> > > Turning this off (via forwardAll="false"), then it outputs all of the
> > > defined mappings (including j_security_check for form auth contexts).
> > > ----- Original Message -----
> > > From: "Bojan Smojver" <bo...@binarix.com>
> > > To: "Tomcat Dev List" <to...@jakarta.apache.org>
> > > Sent: Tuesday, September 25, 2001 5:34 PM
> > > Subject: TC 3.3 + mod_jk + j_security_check
> > >
> > > > Unless this is now implemented automatically in mod_jk, I think it
> would
> > > > be worth mentioning in mod_jk HOWTO about the need to JKMount
> > > > j_security_check when form authentication is used in applications.
> > > >
> > > > I think I should be able to fake a paragraph about it (with examples).
> > > >
> > > > Bojan
> > > >
> > > >
> > >
> > > *----*
> > >
> > > This message is intended only for the use of the person(s) listed above
> > > as the intended recipient(s), and may contain information that is
> > > PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient,
> > > you may not read, copy, or distribute this message or any attachment.
> > > If you received this communication in error, please notify us
> immediately
> > > by e-mail and then delete all copies of this message and any
> attachments.
> > >
> > > In addition you should be aware that ordinary (unencrypted) e-mail sent
> > > through the Internet is not secure. Do not send confidential or
> sensitive
> > > information, such as social security numbers, account numbers, personal
> > > identification numbers and passwords, to us via ordinary (unencrypted)
> > > e-mail.
> >
> >
>
> *----*
>
> This message is intended only for the use of the person(s) listed above
> as the intended recipient(s), and may contain information that is
> PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient,
> you may not read, copy, or distribute this message or any attachment.
> If you received this communication in error, please notify us immediately
> by e-mail and then delete all copies of this message and any attachments.
>
> In addition you should be aware that ordinary (unencrypted) e-mail sent
> through the Internet is not secure. Do not send confidential or sensitive
> information, such as social security numbers, account numbers, personal
> identification numbers and passwords, to us via ordinary (unencrypted)
> e-mail.
Re: TC 3.3 + mod_jk + j_security_check
Posted by Bill Barker <wb...@wilshire.com>.
If the web.xml contains no servlet-mappings, then forwardAll="false" will
generate:
JkMount /myapp/servlet/* ajp13
JkMount /myapp/*.jsp ajp13
and if in addition, the context uses form authorization:
JkMount /myapp/path/to/j_security_check ajp13
You need to set noRoot="false" if you want the ROOT context mappings
generated as well.
Larry has added other options to allow you to specify the directories where
various files go (e.g. mod_jk.so), but I don't remember them off the top of
my head.
----- Original Message -----
From: "Bojan Smojver" <bo...@binarix.com>
To: <to...@jakarta.apache.org>
Sent: Tuesday, September 25, 2001 7:51 PM
Subject: Re: TC 3.3 + mod_jk + j_security_check
> What if the only mapping is for instance:
>
> JkMount /*.jsp ajp13
>
> Will it still work?
>
> Bojan
>
> Bill Barker wrote:
> >
> > This is now implemented automatically in the ApacheConfig module. By
> > default it does:
> > JkMount /myapp/* ajp13
> >
> > Turning this off (via forwardAll="false"), then it outputs all of the
> > defined mappings (including j_security_check for form auth contexts).
> > ----- Original Message -----
> > From: "Bojan Smojver" <bo...@binarix.com>
> > To: "Tomcat Dev List" <to...@jakarta.apache.org>
> > Sent: Tuesday, September 25, 2001 5:34 PM
> > Subject: TC 3.3 + mod_jk + j_security_check
> >
> > > Unless this is now implemented automatically in mod_jk, I think it
would
> > > be worth mentioning in mod_jk HOWTO about the need to JKMount
> > > j_security_check when form authentication is used in applications.
> > >
> > > I think I should be able to fake a paragraph about it (with examples).
> > >
> > > Bojan
> > >
> > >
> >
> > *----*
> >
> > This message is intended only for the use of the person(s) listed above
> > as the intended recipient(s), and may contain information that is
> > PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient,
> > you may not read, copy, or distribute this message or any attachment.
> > If you received this communication in error, please notify us
immediately
> > by e-mail and then delete all copies of this message and any
attachments.
> >
> > In addition you should be aware that ordinary (unencrypted) e-mail sent
> > through the Internet is not secure. Do not send confidential or
sensitive
> > information, such as social security numbers, account numbers, personal
> > identification numbers and passwords, to us via ordinary (unencrypted)
> > e-mail.
>
>
*----*
This message is intended only for the use of the person(s) listed above
as the intended recipient(s), and may contain information that is
PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient,
you may not read, copy, or distribute this message or any attachment.
If you received this communication in error, please notify us immediately
by e-mail and then delete all copies of this message and any attachments.
In addition you should be aware that ordinary (unencrypted) e-mail sent
through the Internet is not secure. Do not send confidential or sensitive
information, such as social security numbers, account numbers, personal
identification numbers and passwords, to us via ordinary (unencrypted)
e-mail.
Re: TC 3.3 + mod_jk + j_security_check
Posted by Bojan Smojver <bo...@binarix.com>.
What if the only mapping is for instance:
JkMount /*.jsp ajp13
Will it still work?
Bojan
Bill Barker wrote:
>
> This is now implemented automatically in the ApacheConfig module. By
> default it does:
> JkMount /myapp/* ajp13
>
> Turning this off (via forwardAll="false"), then it outputs all of the
> defined mappings (including j_security_check for form auth contexts).
> ----- Original Message -----
> From: "Bojan Smojver" <bo...@binarix.com>
> To: "Tomcat Dev List" <to...@jakarta.apache.org>
> Sent: Tuesday, September 25, 2001 5:34 PM
> Subject: TC 3.3 + mod_jk + j_security_check
>
> > Unless this is now implemented automatically in mod_jk, I think it would
> > be worth mentioning in mod_jk HOWTO about the need to JKMount
> > j_security_check when form authentication is used in applications.
> >
> > I think I should be able to fake a paragraph about it (with examples).
> >
> > Bojan
> >
> >
>
> *----*
>
> This message is intended only for the use of the person(s) listed above
> as the intended recipient(s), and may contain information that is
> PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient,
> you may not read, copy, or distribute this message or any attachment.
> If you received this communication in error, please notify us immediately
> by e-mail and then delete all copies of this message and any attachments.
>
> In addition you should be aware that ordinary (unencrypted) e-mail sent
> through the Internet is not secure. Do not send confidential or sensitive
> information, such as social security numbers, account numbers, personal
> identification numbers and passwords, to us via ordinary (unencrypted)
> e-mail.
Re: TC 3.3 + mod_jk + j_security_check
Posted by Bill Barker <wb...@wilshire.com>.
This is now implemented automatically in the ApacheConfig module. By
default it does:
JkMount /myapp/* ajp13
Turning this off (via forwardAll="false"), then it outputs all of the
defined mappings (including j_security_check for form auth contexts).
----- Original Message -----
From: "Bojan Smojver" <bo...@binarix.com>
To: "Tomcat Dev List" <to...@jakarta.apache.org>
Sent: Tuesday, September 25, 2001 5:34 PM
Subject: TC 3.3 + mod_jk + j_security_check
> Unless this is now implemented automatically in mod_jk, I think it would
> be worth mentioning in mod_jk HOWTO about the need to JKMount
> j_security_check when form authentication is used in applications.
>
> I think I should be able to fake a paragraph about it (with examples).
>
> Bojan
>
>
*----*
This message is intended only for the use of the person(s) listed above
as the intended recipient(s), and may contain information that is
PRIVILEGED and CONFIDENTIAL. If you are not an intended recipient,
you may not read, copy, or distribute this message or any attachment.
If you received this communication in error, please notify us immediately
by e-mail and then delete all copies of this message and any attachments.
In addition you should be aware that ordinary (unencrypted) e-mail sent
through the Internet is not secure. Do not send confidential or sensitive
information, such as social security numbers, account numbers, personal
identification numbers and passwords, to us via ordinary (unencrypted)
e-mail.