Maven – Remote repository access through authenticated HTTPS

This document describes how to configure Maven for accessing a remote repository that sits behind an HTTPS server which requires client authentication with certificates. It is expected that this documentation be valid both for Maven 1.x and Maven 2.0.

The problem

You have a server storing a maven repository at addresse https://my.server.com/maven. This server only serves clients authenticated through SSL protocol by a valid certificate signed by an approved certificate authority's certificate which we call the CACert. In the simplest case where the server is used internally by an identified community of users (eg. corporate intranet), the server's certificate is the certificate authority as the server is used only internally.

So we assume that we have access to the trusted certificate in X.509 format stored in a file named:

   /somewhere/in/filesystem/CACert.cert

The client's certificate has been issued by some other mean not described in this document in PKCS#12 format, which is the format that is accepted by browsers (at least Firefox and Internet Explorer) for importation in their keystore. This file is named:

   /home/directory/mycertificate.p12

and we assume it is accessible when launching maven. Note that this file contains the client's private key which may be very sensitive information and so is secured by a password:

   CeRtPwD

The remote repository is referenced either through the pom.xml file (maven2.0) or one of build.properties or project.properties (Maven1.X). In Maven 1.X:

maven.repo.remote=https://my.server.com/maven,http://www.ibiblio.org/maven

The solution

For maven to use this repository, we should take the following steps:

Create a store to hold the server's certificate usings Sun's keytool,
Defines properties to be used by HttpClient for finding keys and certificate

Storing certificate

The following command line imports the certififcate authority's certificate into a JKS formatted key store named trust.jks, the trust store.

$> keytool -v -alias mavensrv -import \
     -file /somewhere/in/filesystem/CACert.cert\
      -keystore trust.jks
Enter keystore password:
Owner: ....
Issuer: ....
Serial number: ....
Valid from: Mon Feb 21 22:34:25 CET 2005 until: Thu Feb 19 22:34:25 CET 2015
Certificate fingerprints:
         MD5:  .......
         SHA1: .....
Trust this certificate? [no]:  yes
Certificate was added to keystore
[Storing trust.jks]
$>

Note that it should be possible to import a full chain of certificates with only one root certificate being trusted but the author did not test it.

Setting properties

The following properties must be set at start of maven to be accessible when HttpClient starts up.

javax.net.ssl.trustStore: the path to the keystore where trusted certificates are stored
javax.net.ssl.trustStoreType: the type of storage for this store, maybe either jks (default) or pkcs12
javax.net.ssl.trustStorePassword: the password protecting the store
javax.net.ssl.keyStore: the path to the keystore where user's private key is stored
javax.net.ssl.keyStoreType: the type of storage for this store, maybe either jks (default) or pkcs12
javax.net.ssl.keyStorePassword: the password protecting the store

Not all the properties must be set depending of your precise settings: type of store may left to default, password may be empty.

Maven 2.0

They may be set either on maven's command-line, in .mavenrc file or in MAVEN_OPTS environment variable. For the setting defined in this document, here is an example .mavenrc file:

MAVEN_OPTS="-Xmx512m -Djavax.net.ssl.trustStore=trust.jks \
                     -Djavax.net.ssl.trustStorePassword=  \
                     -Djavax.net.ssl.keyStore=/home/directory/mycertificate.p12 \
                     -Djavax.net.ssl.keyStoreType=pkcs12 \
                     -Djavax.net.ssl.keyStorePassword=XXXXXX"

For maven 1.X users

Setting these properties in build.properties or project.properties does not work: the properties are needed before any of theses files are opened.

Guide to Remote repository access through authenticated HTTPS