-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Johannes and Mark,
Mark Thomas wrote:
> A valve or a servlet filter is probably your best best. You'll be
> better off with a valve if you want to get at any Tomcat internals but
> a filter will be portable between containers.
>
> I haven't tried to
Johannes wrote:
> I had to try it and...
> It did not work as you already knew.
>
> Is there any other possibility besides writing my own Valve (that no one so
> far has said don't work. But I have no clue how that is done.)
A valve or a servlet filter is probably your best best. You'll be
bette
4 Nov 2006 01:02:14 +0100
To: Tomcat Users List users@tomcat.apache.org
Subject: Re: Tomcat authenticate with BASIC Auth (Pre: Active directory)
> Johannes wrote:
> > That is really a REALLY good idea!
> > And if that works the solution is solved.
>
> Afraid not. It is a bad idea
Johannes wrote:
> That is really a REALLY good idea!
> And if that works the solution is solved.
Afraid not. It is a bad idea and won't work.
Mark
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail:
Pid [EMAIL PROTECTED]
Date: Fri, 03 Nov 2006 14:28:29 +0100
To: Tomcat Users List users@tomcat.apache.org
Subject: Re: Tomcat authenticate with BASIC Auth (Pre: Active directory)
>
> If you deploy the webapp inside another directory that is already
> protected, you can use SingleSignOn to ex
If you deploy the webapp inside another directory that is already
protected, you can use SingleSignOn to execute login via the parent/ROOT
web app?
Tim Funk wrote:
> Out of the box - there is no Valve in Tomcat which requires
> authentication without first consulting web.xml.
>
> As a simple(
Out of the box - there is no Valve in Tomcat which requires
authentication without first consulting web.xml.
As a simple(?) kludge - you could write your own Valve which forces
authentication on anything executed by the Valve: - you'll need to fill
in isAuthenticated(...)
public class Prote
With the lack of reply's I guess that Active directory connections are not used
by anyone here.
I'm making it a bit more simple then and in step one only protect this service
with a simple login / password protection.
Setup: One separate engine only accepting HTTPS connections that needs to be
