SSL BIO/NIO setup with openssl CA puzzle

2012-10-26 Thread Brian Burch
My production tomcat 7.0.26 (and its predecessors back as far as tc 5) have been running with its original SSL server certificate in a JKS keystore for many years. I decided to retire my ancient java-based Certificate Authority and create a new CA using openssl 1.0.1 under ubuntu linux. I

Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)

2012-10-26 Thread André Warnier
Gabriel Huerta Araujo wrote: ... GRAVE: Failed to initialize end point associated with ProtocolHandler [http-bio-8443] java.io.IOException: La configuración SSL no es válida debido a No available certificate or key corresponds to the SSL cipher suites which are enabled. at

Re: SSL BIO/NIO setup with openssl CA puzzle

2012-10-26 Thread Daniel Mikusa
On Oct 26, 2012, at 5:11 AM, Brian Burch wrote: My production tomcat 7.0.26 (and its predecessors back as far as tc 5) have been running with its original SSL server certificate in a JKS keystore for many years. I decided to retire my ancient java-based Certificate Authority and create a

RE: SSL BIO/NIO setup with openssl CA puzzle

2012-10-26 Thread Martin Gainty
Hi Dan if you reference this simple test.jsp does every version of every browser accept the cert as CA cert and properly installs your certificate? %@ page contentType=text/html% html head !-- wait 1 second then download and install cert -- meta http-equiv=refresh content=1;

Re: tomcat 7 PermGen

2012-10-26 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ted, On 10/25/12 7:24 PM, Ted Smith wrote: After upgrading to 7, deploying a new war file often results in PermGen error, much more often than in 6.(with identical JVM settings) I have tried all those JVM settings for perm memory but no help.

Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)

2012-10-26 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gabriel, On 10/25/12 5:42 PM, Gabriel Huerta Araujo wrote: Sorry I forgot to include what below command generates: openssl c_client -connect host:8443 Oops. That should have been s_client, but you already figured that out: I had to run it as:

Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)

2012-10-26 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gabriel, On 10/25/12 5:32 PM, Gabriel Huerta Araujo wrote: My web.xml's connector section originally was: Connector SSLEnabled=true acceptCount=100 clientAuth=false disableUploadTimeout=true enableLookups=false maxThreads=25 port=8443

Re: SSL BIO/NIO setup with openssl CA puzzle

2012-10-26 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian, On 10/26/12 5:11 AM, Brian Burch wrote: I have another system with java-7-openjdk-i386, but I haven't yet done any work on it. This openjdk does not ship with a keytool program, and so I presume it will use openssl. I dunno about the i386

Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)

2012-10-26 Thread Gabriel Huerta Araujo
Hi Christopher I do not understand what you mean with other reply, but I tried openssl s_client -host logangha -port 8443 connect: Connection refused connect:errno=111 Also I tried openssl s_client -connect logangha:8443 And generates same output: connect: Connection refused

Re: Tomcat 7.0.30 CMA, clustering, and SSO

2012-10-26 Thread Josh Gooding
Haha, Scott you're here too? On Thu, Oct 25, 2012 at 2:06 PM, Scott Carlson scott.a.carl...@gmail.comwrote: We've setup TC 7.0.32 with Clustering and Tomcat Container Managed Authentication. HTTPSessions and SSOSessions are clustered across the wire. With logging turned way up, I can see

Tomcat 7 manager quirk?

2012-10-26 Thread Josh Gooding
Hey group, I'm working with Tomcat 7's manager application for text deployments. I am having a bit of a quirky issue here. I am deploying a web application that is approx 75MB as a war file that uses Tomcat's ROOT context. Is there a way that I can get tomcat to NOT start auto-deploying

Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)

2012-10-26 Thread Gabriel Huerta Araujo
I have followed below steps: 1.- Erase keytore keytool -delete -keystore .keystore -storepass x_men_gha 2.- List to verify if it has been deleted. keytool -list -storepass x_men_gha Tipo de almacÚn de claves: JKS Proveedor de almacÚn de claves: SUN Su almacÚn de claves contiene 0 entradas 3.-

Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)

2012-10-26 Thread Igor Cicimov
On 27/10/2012 9:37 AM, Gabriel Huerta Araujo huert...@hildebrando.com wrote: I have followed below steps: 1.- Erase keytore keytool -delete -keystore .keystore -storepass x_men_gha 2.- List to verify if it has been deleted. keytool -list -storepass x_men_gha Tipo de almacÚn de claves:

Re: Implementing SSL and error invocating https://localhost:8443/ (Tomcat 7.0 on Windows 7)

2012-10-26 Thread Gabriel Huerta Araujo
This is my hosts file's content: 10.254.5.1 sigcbd01#10.192.19.1 sigc 10.254.4.63 sdswbd01#10.192.17.66sadigeo 10.254.2.248nsisba01 None of these IP's is my domain. How do I configure dns resolution for such name on my computer to point to the ip of my laptop? As

Re: Tomcat 7 manager quirk?

2012-10-26 Thread Josh Gooding
Igor, I figured it out. If you set the deployOnStartup attribute to true, but the autoDeploy attribute to false, the war files that are in the webapps folder at the time of startup will load. Then you can run the manager via script (command line). Simply pass the undeploy command to the