That's what I thought. Thanks anyway. This is good information!
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Tuesday, February 14, 2012 11:50 AM
To: Tomcat Users List
Subject: Re: controlling Server Authentication only vs M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sanjeev,
On 2/13/12 11:01 PM, Sanjeev Sharma wrote:
> Thanks for your reply. If I set clientAuth="want" will it not ask
> me for a certificate every time I create a new session?
It will not ask for a certificate, but if you provide one, then it wil
authentication, will it force the
browser to prompt for a client certificate?
Sanjeev.
-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, February 13, 2012 4:23 PM
To: Tomcat Users List
Subject: Re: controlling Server Authentication
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 2/13/12 3:39 PM, Pid wrote:
> On 13/02/2012 17:42, Christopher Schultz wrote:
>> Sanjeev,
>>
>> On 2/9/12 11:17 AM, Sanjeev Sharma wrote:
>>> I work on an java web-app running on Tomcat 7. The entire
>>> application is required be doing SSL
On 13/02/2012 17:42, Christopher Schultz wrote:
> Sanjeev,
>
> On 2/9/12 11:17 AM, Sanjeev Sharma wrote:
>> I work on an java web-app running on Tomcat 7. The entire
>> application is required be doing SSL on port 443 (everything is
>> accessed via https://). Two different login options are give
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sanjeev,
On 2/9/12 11:17 AM, Sanjeev Sharma wrote:
> I work on an java web-app running on Tomcat 7. The entire
> application is required be doing SSL on port 443 (everything is
> accessed via https://). Two different login options are given to
> the
Found a solution to this. In case anyone is interested in, I gave my server
two IP addresses and used two connectors with the two IP address in the
"address=" field of the connectors. I set one of them to "clientAuth="true"
and the other "clientAuth=false". I do have to do a "redirect" from o
