id [mailto:p...@pidster.com]
> Sent: Friday, January 27, 2012 4:20 AM
> To: Tomcat Users List
> Subject: Re: SSL client auth
>
> On 26/01/2012 17:37, Harish S K wrote:
>> I am trying to open a https URL on IBM webshpere where ClientAuth is enabled.
>> In response I was get
[mailto:p...@pidster.com]
Sent: Friday, January 27, 2012 4:20 AM
To: Tomcat Users List
Subject: Re: SSL client auth
On 26/01/2012 17:37, Harish S K wrote:
> I am trying to open a https URL on IBM webshpere where ClientAuth is enabled.
> In response I was getting HTTP 403 whereas the URL
On 26/01/2012 17:37, Harish S K wrote:
> I am trying to open a https URL on IBM webshpere where ClientAuth is enabled.
> In response I was getting HTTP 403 whereas the URL can be accessed through
> http. On debugging further, it looks like the client is not sending the
> client certificate in res
On Fri, Mar 19, 2010 at 8:18 AM, rangeli nepal wrote:
> Suppose there is link( https://B) provided on an web application
> hosted at A (tomcat server) that access service on B which through a
> response.redirect(https://B...)
> Once user clicks that link a encrypted channel is established
Thank you. That is something I am not clear about.
Suppose there is link( https://B) provided on an web application
hosted at A (tomcat server) that access service on B which through a
response.redirect(https://B...)
Once user clicks that link a encrypted channel is established between A an
rangeli nepal wrote:
Thank you for your response. I would have definitely not written to this
group, if my question would just related to SSL terminating on Apache. Here
is my scenario:
___
| |
Thank you for your response. I would have definitely not written to this
group, if my question would just related to SSL terminating on Apache. Here
is my scenario:
___
| | |
|
|A
If your SSL terminates on Apache then you are obviously in the wrong
mailing list :)
You have nothing to configure in Tomcat.
On Thu, Mar 18, 2010 at 7:20 PM, rangeli nepal wrote:
> Good Morning Everybody,
>
> Currently I am trying set up a tomcat instance so that it can access web
> service b
