Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Message-ID: <3EC17F46.8020508@joedog.org>
Date: Tue, 13 May 2003 19:27:02 -0400
From: Tim Funk <funkman@joedog.org>
Organization: Human being
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.3) Gecko/20030312
MIME-Version: 1.0
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: Re: combining remote address filter and basic authentication
References: <5.2.0.9.2.20030513152054.056e8560@mail.qrc.com>
In-Reply-To: <5.2.0.9.2.20030513152054.056e8560@mail.qrc.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

AFAIK, there is no elegant way to do this. But but probably want to use a 
filter. The filter will check if the IP range is valid. If the ip range if 
not valid, it will look for the WWW-Authenticate (?) header and decode it 
according to the RFC. If there is no WWW-Authenticate - send a 401 redirect 
challenge back to the client. Google is your firend with respect to the 
topics above.

-Tim


Vladimer Shioshvili wrote:
> What I am trying to do is combine remote address filter and basic 
> authentication in the following way:
> 
> to allow access to anyone with ip address10.*.*.* and for the rest to 
> use basic authentication using users.xml file.
> 
> Has anyone done anything like this? I do mostly form based 
> authentication and this is something new I am facing..
> 
> Thanks,
> Vlad
>  


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org