ssl connector

In server.xml I configured an ssl connector like this: Connector port=8443 address=${jboss.bind.address} maxThreads=100 strategy=ms maxHttpHeaderSize=8192 emptySessionPath=true scheme=https secure=true clientAuth=true keystoreFile=${jboss.server.home.dir}/keystore keystorePass=xx password=yy

SSL Connector + truststore refresh without bouncing tomcat

an user account. The certificate gets added to truststoreFile and other account details are set. My problem is that the SSL Connector will only read the truststoreFile when it is initialized. What I would like to have something monitoring the keystore file for changes and reload

Re: SSL Connector + truststore refresh without bouncing tomcat

://ebxmlrr.sourceforge.net/) to allow the user to register his own certificate when creating an user account. The certificate gets added to truststoreFile and other account details are set. My problem is that the SSL Connector will only read the truststoreFile when it is initialized. What I would like

SSL Connector with client auth in TC 5.5.9

We are switching to TC 5.5.9 in an embedded server. In version 5.0.29, whe configured SSL with client auth as follows: CoyoteConnector connector = new CoyoteConnector(); connector.setAddress( host ); connector.setPort( port ); connector.setSecure(true); connector.setCiphers(

CRL configuration with SSL connector

Is it possible to define a CRL to be checked by tomcat when using SSL ? Thanks for your help, Alain. PS: Where can I find a full description of configuration attributes of the coyote connector ? - To unsubscribe, e-mail:

RE: Tomcat (embedded in JBoss) hangs during startup of SSL connector

: Mittwoch, 17. Dezember 2003 17:27 An: [EMAIL PROTECTED] Betreff: Tomcat (embedded in JBoss) hangs during startup of SSL connector Hi there, I've encountered a strange problem while starting jboss 3.2.1 (including tomcat 4.1.24) with the SSL-Connector enabled on port 443: Symptom: The server hangs

Tomcat (embedded in JBoss) hangs during startup of SSL connector

Hi there, I've encountered a strange problem while starting jboss 3.2.1 (including tomcat 4.1.24) with the SSL-Connector enabled on port 443: Symptom: The server hangs while initializing the SSL-connector and never comes back (at least not for several hours). So the whole start-up processes

need attribute for java key password for ssl connector

I have a customer that has assigned a password to his private key and a separate password to his keystore...and is unwilling to make them the same. I can't get Tomcat (using 4.0) to access the cert in his keystore because I can't figure out what attribute to use to specify the key password. I

SSL Connector attributes

I am trying to find out what all of the possible values are for the 'algorithm' and 'protocol' attributes of the Factory element in the HTTPS connector. I have looked all over the web and have only found a reference to the existence of the 'algorithm' attribute, but no usage examples. Also, the

Re: SSL Connector attributes

That's largely because they depend on your JSSE provider. I believe that most providers will also support 'SSL3' and 'SSL2' as protocol attributes (but I don't recommend either of them, so I won't actually try it :). I know that if you are using IBM's 1.4.x JVM, that you need to set the protocol

tomcat 4.1.12 ssl connector stop responding

i'm using tomcat 4.1.12 on jdsk 1.4.0 as a standalone server with coyote http 1.1 connector having http (8080) connector accessible from internal lan only and https (8443) accessible from external hosts (natted to port 443) after two-three days tomcat stops responding on the https connector

RE: tomcat 4.1.12 ssl connector stop responding

: tomcat 4.1.12 ssl connector stop responding i'm using tomcat 4.1.12 on jdsk 1.4.0 as a standalone server with coyote http 1.1 connector having http (8080) connector accessible from internal lan only and https (8443) accessible from external hosts (natted to port 443) after two-three days tomcat

Non-ssl connector to port 80

I am running tomcat 4.1.8 on redhat 8 and having this problems when i try to bind the non-ssl connector to port 80, whereas if i bind to port 8080 i don't have this problems. Can anybody please help, i am linux novice so don't really knows the work around. Thanks Cheers Stephen

RE: Non-ssl connector to port 80

:[EMAIL PROTECTED]] Sent: Tuesday, January 07, 2003 6:23 PM To: [EMAIL PROTECTED] Subject: Non-ssl connector to port 80 I am running tomcat 4.1.8 on redhat 8 and having this problems when i try to bind the non-ssl connector to port 80, whereas if i bind to port 8080 i don't have this problems. Can

HTTP and SSL Connector port problems

Is there any particular good reason to change HTTP port from 8080 to 80 and the SSL connector port from 8443 to 443? They causing problems for me. Some people are suggesting that we should change the ports. I changed the HTTP Connector port from 8080 to 80 Then I uncommented the SSL Connector

RE: HTTP and SSL Connector port problems

PM To: Tomcat Users List Subject: HTTP and SSL Connector port problems Is there any particular good reason to change HTTP port from 8080 to 80 and the SSL connector port from 8443 to 443? They causing problems for me. Some people are suggesting that we should change the ports

RE: HTTP and SSL Connector port problems

Sorry little typo below pot=port number -Original Message- From: Ralph Einfeldt Sent: Wednesday, November 20, 2002 12:11 PM To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: HTTP and SSL Connector port problems The reason that this is recommende is that you otherwise have

RE: HTTP and SSL Connector port problems

?id=14164 -Original Message- From: Peter Lee [mailto:[EMAIL PROTECTED]] Sent: Mittwoch, 20. November 2002 12:04 To: Tomcat Users List Subject: HTTP and SSL Connector port problems Is there any particular good reason to change HTTP port from 8080 to 80 and the SSL connector port

Re: HTTP and SSL Connector port problems

' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, November 20, 2002 3:33 AM Subject: RE: HTTP and SSL Connector port problems Another good reason to change to 80/443 is the following issue: http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg73342.html http://nagoya.apache.org

Re: HTTP and SSL Connector port problems

Also, everyone has different mileages. Just soemone did not able to figure out, that does not mean it's a bug. Pae Mech P.S. Don't use Tomat 4.1.12 with SSL, upgrade to 4.1.14. Minor? ssl warning bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14164 -- To unsubscribe, e-mail:

RE: HTTP and SSL Connector port problems

Users List Subject: HTTP and SSL Connector port problems Is there any particular good reason to change HTTP port from 8080 to 80 and the SSL connector port from 8443 to 443? They causing problems for me. Some people are suggesting that we should change the ports. But how come

Re: HTTP and SSL Connector port problems

to 4.1.14. Minor? ssl warning bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14164 -Original Message- From: Peter Lee [mailto:[EMAIL PROTECTED]] Sent: Mittwoch, 20. November 2002 12:04 To: Tomcat Users List Subject: HTTP and SSL Connector port problems

RE: HTTP and SSL Connector port problems

: Subject: Re: HTTP and SSL Connector port problems Did I miss something that I should I have changed in some other files or place? All I did was to change the ports number in server.xml On 20 Nov 2002 at 7:33, Pae Choi wrote

RE: HTTP and SSL Connector port problems

To: Tomcat Users List Cc: Subject: Re: HTTP and SSL Connector port problems Did I miss something that I should I have changed in some other files or place? All I did was to change the ports number in server.xml On 20 Nov 2002

RE: HTTP and SSL Connector port problems

before -Original Message- From: Peter Lee [mailto:[EMAIL PROTECTED]] Sent: Wed 11/20/2002 2:12 PM To: Tomcat Users List Cc: Subject: Re: HTTP and SSL Connector port problems Did I miss something that I should I have

SSL Connector port problems

I changed the HTTP Connector port from 8080 to 80 Then I uncommented the SSL Connector section and changed the SSL port from 8443 to 433 These are supposed to be well-known ports. But how come after I made the changes, Tomcat just refused to start? I am on the Win2000 platform. !-- Define

Re: SSL Connector port problems

Those ports you mentioned are privileged ports, I think you can only use them if you have ROOT rights (UNIX) or admin rights (Windoze NT/2000), if you don't have root rights I don´t think Tomcat can bind to a privileged port. Do you start Tomcat as ROOT? Mvh KR -- To unsubscribe, e-mail:

Re: SSL Connector port problems

On 19 Nov 2002, at 11:16, Kristján Rúnarsson wrote: Yes, I did start Tomcat as the administrator, so I have all the rights. Those ports you mentioned are privileged ports, I think you can only use them if you have ROOT rights (UNIX) or admin rights (Windoze NT/2000), if you don't have root

SSL connector constructs incorrect path to SSLServerSocketFactory?

Hello, I am having a problem getting SSL to work with Tomcat 4.0. I have set up the JSSE_HOME variable so that it points to my C:\jsse1.0.2 directory, which contains C:\jsse1.0.2\lib\jnet.jar. I receive the following exception --- Using

RE: Tomcat 4 SSL Connector

: Tomcat 4 SSL Connector Hi, I am currently trying to establish if I can specify my own security provider to be used by Tomcat 4.0.1 instead of the one packaged. I'm led to believe it may be possible (or may in the future be possible) by the server.xml file. When you set up an SSL

Tomcat 4 SSL Connector

Hi, I am currently trying to establish if I can specify my own security provider to be used by Tomcat 4.0.1 instead of the one packaged. I'm led to believe it may be possible (or may in the future be possible) by the server.xml file. When you set up an SSL Connector, you have to specify