Mailing-List: contact users-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@archiva.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Https support
Date: Tue, 23 Sep 2008 17:24:23 -0400
Message-ID: 
 <A9CA6046EDC8DE4EA5BC1ABC9CA3DECFF279DD@mse0be1.mailstreet2003.net>
In-Reply-To: <f345f3480809231400m3d6dcac8h999bf7ecd2125226@mail.gmail.com>
Thread-Topic: Https support
Thread-Index: Ackdv4uvFaKBjUhkSLOD0QcEMHnDFQAAfAag
References: 
 <A9CA6046EDC8DE4EA5BC1ABC9CA3DECFF2792E@mse0be1.mailstreet2003.net>
 <48D93F0C.7050006@apache.org>
 <A9CA6046EDC8DE4EA5BC1ABC9CA3DECFF27992@mse0be1.mailstreet2003.net>
 <f345f3480809231400m3d6dcac8h999bf7ecd2125226@mail.gmail.com>
From: "Kraft, Mike" <Mike.Kraft@teradact.com>
To: <users@archiva.apache.org>

You mean on each client machine that connects to the server (its already =
in the server-side keystore)? Unfortunately that's a little too =
invasive.

So I take it that the real problem has nothing to do with Archiva or =
Tomcat, rather that Maven's wagons simply do not want to accept =
self-signed certificates from the server?

Mike

> -----Original Message-----
> From: Emmanuel Venisse [mailto:emmanuel.venisse@gmail.com]=20
> Sent: Tuesday, September 23, 2008 15:01
> To: users@archiva.apache.org
> Subject: Re: Https support
>=20
> You can add your certificate in your jdk keystore.
>=20
> Emmanuel
>=20
> On Tue, Sep 23, 2008 at 9:18 PM, Kraft, Mike=20
> <Mike.Kraft@teradact.com>wrote:
>=20
> > Yes. Sorry I forgot to mention that...
> >
> > > -----Original Message-----
> > > From: Dennis Lundberg [mailto:dennisl@apache.org]
> > > Sent: Tuesday, September 23, 2008 13:10
> > > To: users@archiva.apache.org
> > > Subject: Re: Https support
> > >
> > > "unable to find valid certification path to requested target"
> > >
> > > Are you perhaps using a self-signed SSL certificate in Tomcat?
> > >
> > >
> > > Kraft, Mike wrote:
> > > > Hi,
> > > >
> > > > I'm new to Archiva and this list, so please forgive me if
> > > this is a dumb question. I would like to use our Archiva
> > > repositories via https. We are running Archiva 1.1.2 in
> > > Tomcat 6. I have set up Tomcat properly for https, and I can
> > > successfully browse the Archiva web app via https. However,
> > > all attempts to download from or deploy to the Archiva
> > > repositories via https or dav:https fail (note that attempts
> > > using unencrypted http or dav:http succeed).
> > > >
> > > > For example, when using dav:https and mvn deploy, I get
> > > this error on the command line:
> > > > [INFO] Error deploying artifact: Failed to create
> > > destination WebDAV collection (directory):
> > > /archiva/repository/internal/com/teradact/testBuild/0.20.0
> > > >
> > > > unable to find valid certification path to requested target
> > > > [INFO]
> > > --------------------------------------------------------------
> > > ----------
> > > > [INFO] Trace
> > > > org.apache.maven.lifecycle.LifecycleExecutionException:
> > > Error deploying artifact: Failed to create destination WebDAV
> > > collection (directory):
> > > /archiva/repository/internal/com/teradact/testBuild/0.20.0
> > > >     at
> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa
> > > ls(DefaultLifecycleExecutor.java:583)
> > > > ...
> > > >
> > > > With just https:
> > > > [INFO] Error deploying artifact: Error transferring file
> > > (directory):
> > > /archiva/repository/internal/com/teradact/testBuild/0.20.0
> > > >
> > > > unable to find valid certification path to requested target
> > > > [INFO]
> > > --------------------------------------------------------------
> > > ----------
> > > > [INFO] Trace
> > > > org.apache.maven.lifecycle.LifecycleExecutionException:
> > > Error deploying artifact: Error transferring file
> > > (directory):
> > > /archiva/repository/internal/com/teradact/testBuild/0.20.0
> > > >     at
> > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoa
> > > ls(DefaultLifecycleExecutor.java:583)
> > > > ...
> > > >
> > > > Archiva's own logs show nothing for these events.
> > > >
> > > > Have I missed something? Is there any way to set up Archiva
> > > and/or Maven so https will work?
> > > >
> > > > Thanks in advance,
> > > > Mike
> > >
> > >
> > > --
> > > Dennis Lundberg
> > >
> >
>=20