Eclipse 3.3.1.1
Vault Client 4.1.1
Vault Server 4.1.1
Intial Problem: When trying to Get Latest Version of repository to a developer machine using Vault Client or importing project into Eclipse IDE, the firewall would flag various .jpg files as malformed which initiated the following error in the Vault log.
----7/16/2008 11:50:35 AM jbrown--mypc.mysite.com(10.33.9.82)--SSL Disabled Critical Error downloading file! The remote host closed the connection. The error code is 0x80072746.
This problem seemed to be caused by the way Vault was using the fetch for the file because these .jpg files load fine on the site using the browser - which also ports through the firewall.
Partial Solution: To bypass the firewall challenge, we created a SelfSignedSSL (free- since this is mainly for internal purposes) on the server and attached it to the IIS instance of Vault. We then used the Vault Client to connect via SSL to the repository which prompted the unsigned certficate error - did we want to accept or not (we did). The Vault Client retrieved the latest version like a champ and we thought we were on our way.
New Problem: The Eclipse plug-in does not seem to prompt for accepting an unsigned certificate like the Valut Client does and the login fails, so we are unable to connect to the repository through the IDE.
Question 1: Is there another way to bring the project into the IDE once it's loaded on the developer's machine, then have it connect to Vault?
Question 2: Would it be possible to program the Eclipse plug-in to prompt for accepting the unsigned cert?
Thanks as always,
Jack
Problem with Eclpise plug-in and Self-Signed SSL
Moderator: SourceGear
Sent me in the right direction.
Because the SSL cert was self-signed (no authority), we had to first convert it to a .pem format using openssl, reorder the certificate and key as they appeared in the file, then finally import into Java. Prior to the conversion and reorder, the keytool was generating an "Input not an x.509 certficate" error.
The technique is described here.
http://dev2dev.bea.com/pub/a/2006/08/pf ... rmats.html
For future folks' benefit.
Thanks for the lead.
Because the SSL cert was self-signed (no authority), we had to first convert it to a .pem format using openssl, reorder the certificate and key as they appeared in the file, then finally import into Java. Prior to the conversion and reorder, the keytool was generating an "Input not an x.509 certficate" error.
The technique is described here.
http://dev2dev.bea.com/pub/a/2006/08/pf ... rmats.html
For future folks' benefit.
Thanks for the lead.