Error validating server certificate for

Clone SSL SVN Repository After Accepting Certificate: Depending on how many files are in the repository it may take awhile to clone but you now have successfully cloned a SSL SVN repository.

Use the fingerprint to validate the certificate manually!

Certificate information: – Hostname: net – Valid: from Mon, GMT until Tue, GMT – Issuer: SVN, – Fingerprint: ac:a0:8d::7c::83:f0:2d:f::f3:2d:cc (R)eject, accept (t)emporarily or accept (p)ermanently? Now the certificate will be stored permanently and now it should work without any intervention.

This is one of the most common error seen during svn sync.

I myself spent some pretty good time to figure out the perfect solution for this error.

Error validating server certificate for '': - The certificate is not issued by a trusted authority.

Use the fingerprint to validate the certificate manually! On "teneight-slave” and "tennine-slave"s the svn info runs fine when used with a “sudo”, however without sudo (user=local) it keeps prompting to take action with the new certificates, (reject, accept etc) every time you run the svn info command.

Certificate information: - Hostname: somename.server1.- Valid: from Aug 6 2014 GMT until Aug 3 2024 GMT - Issuer: R&D, MYGROUP, KOBE, KOBE, JP - Fingerprint: 49:0C:7B: A: A6: A0:2B:91: D3: FB: DB: EC:66: AA:: B: CE(R)eject or accept (t)emporarily? Committed revision 1.====================================================When I checkout the same project by Cornerstone, Cornerstone will prompt me with "1.8 working copies may not be compatible with other subversion apps on this Mac. Cornerstone includes a fix but this issue may affect other Subversion clients.

As previous versions are not affected by this bug, the user of 1.7 working copies is recommended..." If I click "Check out Anyway" button, the project will be checkout correctly.

In this example I was attempting to sync a repository using SVN to a folder on the desktop of my Macbook Pro running OSX Mountain Lion.

Tags: , ,