Sponsored Content
Special Forums Cybersecurity how to configure ssl for tomcat 6 Post 302398663 by mcW on Thursday 25th of February 2010 07:57:26 AM
Old 02-25-2010
how to configure ssl for tomcat 6

Hi,

my server is running a tomcat servlet container.
yesterday a bought a ssl-certificate from geotrust.com.

i got a private-key file and a cert-file (PKCS10).

i followed the instructions on Apache Tomcat 6.0 - SSL Configuration HOW-TO

first, i created a keystore:
Code:
$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA

after this uncomment this part in the server.xml:
Code:
<-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
<Connector 
           port="443" maxThreads="200"
           scheme="https" secure="true" SSLEnabled="true"
           keystoreFile="/root/.keystore" keystorePass="mypw"
           clientAuth="false" sslProtocol="TLS"/>

/root/.keystore really exists and i used the pw i created the keystore with.

now i restarted the server. everythings works fine, i got a connection on port 443.
after this i wanted to install the certificate i got from geotrust.

before that, i installed the root certifcate i got from this page: https://www.geotrust.com/resources/r...tes/index.html (Equifax Secure Certificate Authority (Base-64 encoded X.509)
Code:
keytool -import -alias root -keystore /root/.keystore \
    -trustcacerts -file equifax.cer

the system told me, that this certificate already exists, i decided to overwrite it.

now in tried to install my certifcate:
Code:
keytool -import -alias tomcat -keystore /root/.keystore \
    -file www.mydomain.cert

but i got this error msg:
Code:
keytool error: java.lang.Exception: Public keys in reply and keystore don't match

i dont know what i did wrong. and whatfor do i need my private-key file?


EDIT: i solved the problem. old.nabble.com/tomcat6-and-https-td27515107.html

Last edited by mcW; 02-25-2010 at 09:42 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

implicit ssl vs explicit ssl

Can someone explain the difference between the two. Thanks (1 Reply)
Discussion started by: jerardfjay
1 Replies

2. UNIX for Dummies Questions & Answers

to enable POP3(ssl) and SMTP(ssl) in Squid

i have configured Squid proxy server in Fedora 8 with two network interfaces. HTTP, HTTPS, FTP are working fine but we are unable to download mails using mail clients from mail server with POP3(ssl) and SMTP(ssl). so please someone help us how to enable pop and smtp in Squid. (1 Reply)
Discussion started by: praneel2k
1 Replies

3. Red Hat

Configure Tomcat to syslog

Hi ALL, Thanks for previous replies.. This thread is regarding tomcat logs -> Syslog Server. I have followed this doc:- Red Hat Knowledgebase: How do I log Tomcat output to a remote syslog server? But no success.. any clues? Thanks alot! Sudhir (3 Replies)
Discussion started by: sidhurana
3 Replies

4. Web Development

Apache, cgi script run twice when ssl, once when not ssl

I have interesting problem. https:/host/some/x.cgi - this script has run twice when I call this url But http:/host/some/x.cgi work fine, only once. Output is text/plain. If I change output format to the Content-type text/html, then both urls works fine - executed only once. (2 Replies)
Discussion started by: kshji
2 Replies

5. Solaris

tomcat installation

hi.. i need to install tomcat on my solaris 10 x86 OS.. can u please guide me .. i know that tomcat is already present in solaris 10 x86.. tell me how to enable it.. tel me as soon as possible.. i tried but its throwing me the following error.. The JAVA_HOME environment variable is not... (5 Replies)
Discussion started by: senkerth
5 Replies

6. IP Networking

configure apache to work with ssl

Hi, I need help to configure the apache to work with ssl. I have managed to create self-signed certificate according to the instruction in the following link. So I have the crt file and the key file. however when I add: <Virtualhost *:443> SSLEngine on ... (1 Reply)
Discussion started by: programAngel
1 Replies

7. Solaris

configure iplanet DS for SSL without console?

Hey guys, Is it possible to configure iplanet DS for SSL without the DS console? I cannot find any documentation regarding it. The iplanet DS document only references using the DS console which I do not have. In Sun One, you can use dsadm to import certs however that is not available in iplanet... (0 Replies)
Discussion started by: s ladd
0 Replies

8. Solaris

Tomcat..Unable to deploy application remotely in tomcat

Hi, We have upgrade tomcat from 5.0.20 to 7.0.33 and made changes to server.xml file according to newer version.. how ever the upgrade went fine and now i am unable to deploy application remotely.. it is giving 403 access denied error.. we have seperate appbase directory mentioned in server.xml..... (0 Replies)
Discussion started by: phani4u
0 Replies

9. Red Hat

SSL Certificate Renewal on Tomcat

Hi, I want to renew the ssl certificate for one of my application on tomcat without down time. I want to know what would the possible impacts for the users who currently have sessions to the app. Regards, Arumon (1 Reply)
Discussion started by: arumon
1 Replies

10. Linux

Apache wildcard ssl on subdomain serves same page for non ssl virtualhosts

Issue observed: I have configured ng.my-site.com using widlcard ssl cert. When I hit https://www.my-site.com it loads ng.my-site.com website! please advise if I missed any concept / configs... Thank you! httpd.conf <VirtualHost *:80> ServerName www.my-site.com ServerAdmin... (0 Replies)
Discussion started by: ashokvpp
0 Replies
lprng_certs(1)							lprng_certs command						    lprng_certs(1)

NAME
lprng_certs - lprng SSL certificate management SYNOPSIS
lprng_certs option Options: init - make directory structure newca - make new root CA defaults - set new default values for certs gen - generate user, server, or signing cert index [dir] - index cert files verify [cert] - verify cert file encrypt keyfile - set or change keyfile password DESCRIPTION
The lprng_certs program is used to manage SSL certificates for the LPRng software. There SSL certificate structure consists of a hierarchy of certificates. The LPRng software assumes that the following types of certificates will be used: CA or root A top level or self-signed certificate. signing A certificate that can be used to sign other certificates. This is signed by the root CA or another signing certificate. user A certificate used by a user to identify themselves to the lpd server. server A certificate used by the lpd server to identify themselves to the user or other lpd servers. Signing Certificates All of the signing certificates, including the root certificate (root CA), /etc/lprng/ssl.ca/ca.crt, are in the same directory as the root CA file. Alternately, all of the signing certs can be concatenated and put into a single file, which by convention is assumed to have the same name as the root CA file, /etc/lprng/ssl.ca/ca.crt. The ssl_ca_file, ssl_ca_path, and ssl_ca_key printcap and configuration options can be used to specify the locations of the root CA files, a directory containing the signing certificate files, and the private key file for the root CA file respectively. The root certificate (root CA file) /etc/lprng/ssl.ca/ca.crt has a private key file /etc/lprng/ssl.ca/ca.key as well. By convention, the private keys for the other signing certificate files are stored in the certificate file. The OpenSSL software requires that this directory also contain a set of hash files which are, in effect, links to these files. By default, all signing certificates are assumed to be in the same directory as the root certificate. Server Certificates The certificate used by the lpd server are kept in another directory. These files do not need to have hash links to them. By convention, the private keys for these certificate files are stored in the certificate file. The server certificate file is specified by the ssl_server_cert and has the default value /etc/lprng/ssl.server/server.crt. This file contains the cert and private key. The server cer- tificate password file is specified by the ssl_server_password option with the default value and contains the password used to decrypt the servers private key and use it for authentication. This key file should be read only by the lpd server. User Certificates The certificates used by users are kept in a separate directory in the users home directory. By convention, the private keys for these certificate files are stored in the certificate file. The user certificate file is specified by the LPR_SSL_FILE environment variable, otherwise the ${HOME}/.lpr/client.crt is used. The pass- word is taken from the file specified by the LPR_SSL_PASSWORD environment variable, otherwise the ${HOME}/.lpr/client.pwd file is read. USING LPRNG_CERTS The organization of the SSL certificates used by LPRng is similar to that used by other programs such as the Apache mod_ssl support. The lprng_certs program is used to create the directory structure, create certificates for the root CA, signing, user and servers. In order to make management simple, the following support is provided. lprng_certs init This command creates the directories used by the lpd server. It is useful when setting up a new lpd server. lprng_certs newca This command creates a self-signed certificate, suitable for use as a root CA certificate. It also sets up a set of default values for other certificate creation. lprng_certs defaults This command is used to modify the set of default values. The default values are listed and should be self-explanatory, except for the value of the signer certificate. By default, the root CA can be used to sign certificates. However, a signing certificate can be used as well. This allows delegation of signing authority without compromising the security of the root CA. lprng_certs gen This is used to generate a user, server, or signing certificate. lprng_certs index This is used to create the indexes for the signing certificates. lprng_certs verify [cert] This checks the certificate file using the Openssl openssl verify command. lprng_certs encrypt keyfile This removes all key information from the key file, reencrypts the key information, and the puts the encrypted key information in the file. LPRng OPTIONS Option Purpose ssl_ca_path directory holding the SSL signing certs ssl_ca_file file holding the root CA or all SSL signing certs ssl_server_cert cert file for the server ssl_server_password file containing password for server server ${HOME}/.lpr/client.crt client certificate file ${HOME}/.lpr/client.pwd client certificate private key password ENVIRONMENT VARIABLES
LPR_SSL_FILE client certificate file LPR_SSL_PASSWORD client certificate private key password EXIT STATUS
The following exit values are returned: zero (0) Successful completion. non-zero (!=0) An error occurred. SEE ALSO
lpd.conf(5), lpc(8), lpd(8), checkpc(8), lpr(1), lpq(1), lprm(1), printcap(5), lpd.conf(5), pr(1), lprng_certs(1), lprng_index_certs(1). AUTHOR
Patrick Powell <papowell@lprng.com>. HISTORY
LPRng is a enhanced printer spooler system with functionality similar to the Berkeley LPR software. The LPRng developer mailing list is lprng-devel@lists.sourceforge.net; subscribe by visiting https://lists.sourceforge.net/lists/listinfo/lprng-devel or sending mail to lprng- request@lists.sourceforge.net with the word subscribe in the body. The software is available via http://lprng.sourceforge.net LPRng 2006-12-09 lprng_certs(1)
All times are GMT -4. The time now is 05:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy