It is possible to configure your Subversion client to ignore such warnings, but I don't think that is a very good idea.
If it's not possible to fix the server, you will need to customize the server trust evaluation to allow the connection to proceed without completely undermining the user's security.
is a discussion of how to work around specific server trust evaluation problems.
You can also customize server trust evaluation for the opposite reason, that is, to make the connection more secure. This is the first step in establishing a secure connection.
The second step, which is just as critical, is for you to examine the certificate you got from the server to decide whether it matches the server you are expecting to talk to.
You should read this document if you're creating an i OS or Mac OS X program that uses HTTPS, TLS or SSL to talk to a server securely, and you need to resolve a server trust evaluation failure or enforce a stricter form of server trust evaluation.
Domain=NSURLError Domain Code=-1202 "The certificate for this server is invalid.
You might be connecting to a server that is pretending to be “example.com” which could put your confidential information at risk." User Info=0x14a730 Blindly following this advice is a serious mistake.
HTTPS (actually, the underlying TLS protocol) offers two important security guarantees, and if you disable server trust evaluation you totally invalidate one of these guarantees.
In practice this involves checking that the DNS name that you are attempting to connect to matches the DNS name in the certificate.
There are, however, a few wrinkles: Important: The first three criteria apply to all certificates in the path of certificates leading from the server certificate to the trusted anchor.
Once you understand the problem you'll likely find that the easiest solution is to fix the server.