Java in general is very picky about certificates. If you want to use self-signed certificated you usually need to jump through all kinds of hoops to get it working, if it's even possible. The easiest solution by far it to get a real certificate.
Kraft, Mike wrote: > 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:[EMAIL PROTECTED] >> Sent: Tuesday, September 23, 2008 15:01 >> To: [email protected] >> Subject: Re: Https support >> >> You can add your certificate in your jdk keystore. >> >> Emmanuel >> >> On Tue, Sep 23, 2008 at 9:18 PM, Kraft, Mike >> <[EMAIL PROTECTED]>wrote: >> >>> Yes. Sorry I forgot to mention that... >>> >>>> -----Original Message----- >>>> From: Dennis Lundberg [mailto:[EMAIL PROTECTED] >>>> Sent: Tuesday, September 23, 2008 13:10 >>>> To: [email protected] >>>> 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 >>>> > -- Dennis Lundberg
