I ran into this same snag.
The docs state that in the server.xml file where you activate SSL you should put
"ClientAuth=true". Make that "false".
Basically what is happening is that the server is asking the browser to identify
itself with a certificate. Most people do not have a certificate
I have followed the instructions in server.xml for configuring SSL with Tomcat.
When I try to access the SSL connection at http://ip.add.re.ss:8443, the server
thinks about it, then my browser (IE5) displays and empty certificates box for
me the select the certificate I want to use. The
Ok, let's ask this. Has the current binary for Tomcat 3.2.1 been compiled to use
JSSE? I've seen posts in the archive that indicate previous binaries were not,
but that may have been during beta.
I am using the Tomcat 3.2.1 binary which I downloaded on Monday. We want a
standalone
Ok, after much beating of my head against my desk, I think I have figured it
out.
In the tomcat-ssl-howto, the keytool program is used at the beginning of the
process, and at the end of the process. What appears to have been forgotten is
that the second time keytool is used, it needs to be run
I have seen in the archives that it is possible to run multiple instances of
Tomcat using different ports. What I need to do is run multiple instances of
Tomcat 3.2.1 standalone with SSL each on a different IP address on the same
machine.
Each instance must be completely separate from all
Carlos,
Take a look at the test-tomcat.xml file in the conf directory of tomcat. In that
file you will see several lines specifying "property name="blah"
value="stuff"/ and then later on you will see something like
"variable.to.set="${blah}"/. For example:
target name="init"
property
Has anyone installed Tomcat 4 standalone with SSL? After trying to get Tomcat
3.2.1 to successfully work standalone with SSL I decided to take a look at
Tomcat 4.0m5. From what I have been able to glean from the documentation I have
been able to find, it appears that TC4 may be able to offer us
My frustration level has reached it's peak with this, so if I come across as
being a little short, I apologize in advance. I have not been able to find
anything in the archives about this, and previous posts have not netted much to
help me with this problem. Perhaps it was just the holidays, so
Bingo! I added the "inet" variable to each HttpConnectionHandler in my
server.xml files (three times per file, once for http, once for https and once
for the "internal" connector on port 8007). Tomcat successfully (I think)
started on two different IP addresses. The logs showed some messages
If each instance is using its own IP address and each server has its own
server.xml file, would it still be necessary to change the
Ajp1[2,3]ConnectionHandler port number?
Dion Vansevenant
Internetwork Administrator
MRO.com
|+--
|| Ralph
Sorry, no luck. Must be on separate IP addresses. See the post from Ritchie
Young on Jan 10 in response to this thread. That's what worked for me, maybe
it'll work for you too.
Dion Vansevenant
Internetwork Administrator
MRO.com
|+
|| Aleksey
No, there is only one NIC and it is configured with multiple IP's (aliased?
multihomed?) This is new to me, although the company has been doing it for a
while. Solaris lets us define eth0, then eth0:1, eth0:2, etc., each with it's
own IP address. We have some servers with upwards of 10 IP's on
12 matches
Mail list logo
