Secure service in Java Web server 2.0

Question

Hi all, I have installed a Java Web Server 2.0 without the secure service running, and everything works just fine.
Then I make a self-signed certificate with authstore, using key size 1024, MD5withRSA, hostname: <my computer> (testing on local net (maybe this is what fails?)), and all the other stuff. All looks good and certificate info looks like this:
Subject Information: CN=yodopc1, OU=SW dept, O=Yodoba, L=Z?rich, ST=Z?ric, C=CH
Issuer Information: CN=yodopc1, OU=SW dept, O=Yodoba, L=Z?rich, ST=Z?ric, C=CH
Dates Valid: Thu Jun 28 10:19:35 CEST 2001 --> Wed Sep 26 10:19:35 CEST 2001
Algorithm: MD5withRSA
Serial Number: 993716375
Then I exit, and restart (even tried rebooting machine).
Start webserver, type inn key password, and login to the Server admin applet. There it says:
Service -------------- Status ------ Port -- Network Address
Java web server ------ Terminated - -------
- Web service -------- Unknown --- 80 ----
- Secure Web service - Unknown --- 7070 --
If I try to start the server, it runs for about ten seconds before it is back to the same state again. Of course trying to access server through http(s)://localhost(:7070) results in a "Cannot find server..." If I delete the keys file in <JWS-root>, everything is back to where it was before I started creating the certificate.
I have seen that there are a lot of old (1-2 years old) Posts with similar and perhaps related issues, but none of witch have any replies that finds a solution. Hopefully someone can help my now...
All help and suggestion are Greatly appriciated.
Sjur

Answer 1

Hi Sjurba,
Please follow this URL:
http://www.sun.com/software/jwebserver/faq/faq.html#f6
http://docs.iplanet.com/docs/manuals/messaging/sims35/install/postwa.doc6.html
Also read the below.
Client side workaround: Use Netscape Communicator 4.x instead of Netscape Navigator 3.x.
Java Web Server workaround: Use the VeriSign root certificate that is shipped in Java Web Server 1.1. Follow these instructions:
1.Copy or save the file named keys, located in the top level directory of your Java Web Server installation, to a secure place (for example, a floppy disk).
2.Locate the secure server certificate that VeriSign sent you.
3.Install Java Web Server 1.1 in a temporary directory. You don't need to run this server--you only need to run AuthStore to regenerate the keys file. (The install of
Java Web Server 1.1 does need not be on the same machine as the install of the Java Web Server 1.1.x that has the problem).
For the remainder of these instructions, 1.1.x server root is the installation directory of the Java Web Server 1.1.x that shows the problem. 1.1 server root is the
installation directory of Java Web Server 1.1
4.Copy the keys file from 1.1.x server root/ to 1.1 server root/.
5.Run AuthStore under 1.1 server root. AuthStore is in the bin directory. You will need to type in the server passphrase to launch AuthStore.
6.From the scrolling list, select the key that corresponds to the secure server certificate from VeriSign.
7.Click Import and type the full path of the certificate that you received from VeriSign.
8.Click Save to write a new keys file under 1.1 server root.
9.Click Exit.
10.Copy the new keys file from 1.1 server root/ to 1.1.x server root/.
11.Restart the Java Web Server 1.1.x under 1.1.x server root.
I hope this will help you.
Thanks
Bakrudeen
Technical Support Engineer
Sun MicroSystems Inc, India