Project

General

Profile

Actions

Bug #235

closed

ssl support for metacat (https)

Added by Matt Jones over 23 years ago. Updated over 22 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jivka Bojilova
Category:
metacat
Target version:
Start date:
06/05/2001
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
235

Description

Need support for clients to connect to metacat using ssl. Need to determine a
reasonable way of generating and assigning certificates (probably we generate
them and provide a central registry of metacat servers where clients can get the
public keys).

Need support for metacat to contact LDAP over SSL to make this a secure connection.


Related issues

Blocked by Morpho - Bug #201: add https support to client frameworkResolvedDan Higgins04/09/2001

Actions
Blocked by Metacat - Bug #185: replication security holeResolvedJivka Bojilova04/09/2001

Actions
Actions #1

Updated by Jivka Bojilova over 23 years ago

These are the things that should be done on the server for Metacat to
communicate through HTTPS:

1. in $TOMCAT_HOME/conf/server.xml uncomment this part for SSL suport:

<Connector className="org.apache.tomcat.service.PoolTcpConnector">
<Parameter name="handler"
value="org.apache.tomcat.service.http.HttpConnectionHandler"/>
<Parameter name="port"
value="8443"/>
<Parameter name="socketFactory"
value="org.apache.tomcat.net.SSLSocketFactory" />
</Connector>

but comment the part for the normal HTTP.

2. Download JSSE and install JSSE jars by coping jart.jar, jnet.jar, jsse.jar to
$JAVA_HOME/jre/lib/ext.

3. Edit $JAVA_HOME/jre/lib/security/java.security by adding one line for Sun's
CSProvider "SunJSSE":
security.provider.2=com.sun.net.ssl.internal.ssl.Provider

4. Do: keytool -genkey -alias tomcat -keyalg RSA -keystore /opt/httpd/.keystore
RSA is essential to work with Netscape and IIS. Use "changeit" as password. ( or
add keypass attribute to change it. ) You don't need to sign the certificate.

This generates key pair with self-signed certificate holding the public key. You
don't need to sign the certificate. Check with:
keytool -list -alias tomcat

5. vi $TOMCAT_HOME/bin/tomcat.sh. In there add the HTTPS handler by:
TOMCAT_OPTS="-Djava.protocol.handler.pkgs=edu.ucsb.nceas.protocols|com.sun.net.s
sl.internal.www.protocol"

6. Restart Tomcat to take effects.

7. In order for the client to trust that certificate you should export it in a
file. Send that file to the client who then should import it as a trusted
certificate.
keytool -export -alias tomcat -file dev.cer -keystore /opt/httpd/.keystore
dev.cer is the file to be sent to the client.

Actions #2

Updated by Jivka Bojilova over 23 years ago

2. Download JSSE and install JSSE jars by coping jart.jar, jnet.jar, jsse.jar to
$JAVA_HOME/jre/lib/ext and to $TOMCAT_HOME/lib.

Actions #3

Updated by Jivka Bojilova over 23 years ago

DONE

Actions #4

Updated by Redmine Admin over 11 years ago

Original Bugzilla ID was 235

Actions

Also available in: Atom PDF