Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3F11D1803C for ; Wed, 5 Aug 2015 08:44:49 +0000 (UTC) Received: (qmail 9503 invoked by uid 500); 5 Aug 2015 08:44:45 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 9451 invoked by uid 500); 5 Aug 2015 08:44:45 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 9441 invoked by uid 99); 5 Aug 2015 08:44:45 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Aug 2015 08:44:45 +0000 Received: from [192.168.23.9] (host81-156-41-163.range81-156.btcentralplus.com [81.156.41.163]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 083421A009C for ; Wed, 5 Aug 2015 08:44:43 +0000 (UTC) Message-ID: <55C1CCF4.3050906@apache.org> Date: Wed, 05 Aug 2015 09:44:36 +0100 From: Mark Thomas User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Tomcat Users List Subject: Re: FIPS compliancy on Tomcat 7.00.062 References: <55C080BC.1070000@apache.org> <55C0B491.8050605@apache.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 05/08/2015 07:32, Nikitha Benny wrote: > Hi Mark, > > When I try to run Tomcat on the https server port: > > *https://:8444/* > > It says as below: > ---------- > > *SSL connection error* > > *ERR_SSL_PROTOCOL_ERROR* > > *Unable to make a secure connection to the server. This may be a problem > with the server, or it may be requiring a client authentication certificate > that you don't have* > *------------* That is the client side. What about server side logs? > We have set the client authentication to False, so it does not need any > client authorized certificate. I recommend you run https://www.ssllabs.com/ssltest/ against your server. That will tell you if you have a server side issue, a client side issue or simply a mismatch between the two. Mark > > Regards, > Nikitha > > On Wed, Aug 5, 2015 at 10:07 AM, Nikitha Benny > wrote: > >>> But still Tomcat does not run on the https port. >> >> As in, when we run Tomcat on the https server port it does not display the >> page. >> Where as it goes through fine on the http port. The url opens. >> >> >> >> On Tue, Aug 4, 2015 at 6:18 PM, Mark Thomas wrote: >> >>> On 04/08/2015 13:19, Nikitha Benny wrote: >>>> Hello Mark, >>>> >>>> Thanks for your valuable suggestion. >>>> >>>> We were successful in creating the pkcs12 keystore which picks up >>> SHA256 as >>>> shown below: >>> >>> >>> >>>> But still Tomcat does not run on the https port. >>> >>> Define "does not run". >>> >>>> Any clue as to why this happens? >>> >>> Based on the information provided so far, no. >>> >>>> The protocol I am using is* "org.apache.coyote.http11.Http11Protocol".* >>> >>> OK. That is the HTTP BIO connector. >>> >>>> Could it be because I am not using an APR connector protocol? >>> >>> No. >>> >>> Mark >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org >>> For additional commands, e-mail: users-help@tomcat.apache.org >>> >>> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org