Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of aw@ice-sa.com designates
 212.85.38.228 as permitted sender)
Message-ID: <4CBDB2BB.7010409@ice-sa.com>
Date: Tue, 19 Oct 2010 17:01:15 +0200
From: =?ISO-8859-1?Q?Andr=E9_Warnier?= <aw@ice-sa.com>
Reply-To: Tomcat Users List <users@tomcat.apache.org>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Source Address based Realms
References: <BC2F8964429F14468EA0E6D6CF00E8C9BA4C5F@EXHQ.corp.stratus.com>
In-Reply-To: <BC2F8964429F14468EA0E6D6CF00E8C9BA4C5F@EXHQ.corp.stratus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Aggarwal, Ajay wrote:
> I need to treat my clients differently depending on where they came
> from. I need to trust all requests coming locally (i.e. from
> 127.0.0.1/localhost) and not require them to authentication. However all
> external requests need to go through authentication. Is there a way to
> configure Realms in Tomcat to accommodate this? 
> 
>  
> 
> Is there another way to achieve this, i.e. without using Realms or
> missing valve/filters with Realms?
> 
>  
Maybe phrasing the problem in a different way would throw another light on the issue :

You want to automatically authenticate requests coming from a given IP (or IP range), for 
example by authenticating them as user "local", and not do this for other requests, which 
then would have to go through a normal authentication.

Since I am more familiar with Apache httpd than with Tomcat, I will ask if by any chance 
you are already fronting Tomcat with another webserver ?


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