Hello Kevin,

I don't think the ClientAuth EKU is directly relevant here. Your server
certificate on httpd acts as a server certificate and the certificate most
likely has the ServerAuth EKU. Moreover, the warning in the SVN client
explicitly says "The certificate *is not issued by a trusted authority*",
so I think the root cause is that the client is unable to build a chain
from your new server certificate to a root certificate it trusts.

I would suggest that you reach out to GoDaddy support for assistance
because some knowledge of their CA is needed to advise further. As a wild
guess, I think that you might need to choose
another SSLCertificateChainFile from https://certs.godaddy.com/repository
like a cross-signed 'gd_bundle_dv-*r1-g2*.crt.pem' which *maybe* will help
the client to build certificate trust to a root certificate known/trusted
by your client OS. In the article
<https://godaddy.com/help/why-is-godaddy-removing-clientauth-eku-and-transitioning-to-the-r1-root-hierarchy-for-dv-tls-issuance-42783>,
they say "...  we rely on a *cross-signed trust path back to the
already-trusted G2 root.*" I don’t know exactly which bundle matches your
certificate, because that depends on GoDaddy’s CA setup. If the suggestion
doesn’t help, I would contact GoDaddy support for further assistance.

Thank you!

On Thu, 19 Nov 2026 at 16:49, Kevin Lew <[email protected]> wrote:

> Pavel;
>
>
>
> Thank you for responding.
>
>
>
> I did include the Chain File (gd_bundle) when I updated the certificate.
>
>
>
> SSLCertificateFile /etc/pki/tls/certs/ddci.crt
>
> SSLCertificateKeyFile /etc/pki/tls/private/ddci.key
>
> SSLCertificateChainFile /etc/pki/tls/certs/gd_bundle.crt
>
>
>
> Everything web browser is fine.
>
> Subversion and subversion related scripts are giving us the error.
>
>
>
> I believe this is due to the removal of the  ClientAuth EKU.
>
> This leads me to believe I will need another certificate to make up for
> this.
>
>
>
> Do you know of any documentation out there that could guide me setting up
> a certificate with the ClientAuth EKU?
>
>
>
>
>
> Yes.  I am aware we are running a very old version of svn.  Unfortunately
> the upgrade process has been very challenging.
>
> We plan on upgrading but need to keep this going until we do.
>
>
>
> I really appreciate you responding.
>
>
>
> Thank you.
>
>
>
>
>
> *From:* Pavel Lyalyakin <[email protected]>
> *Sent:* Wednesday, November 18, 2026 4:45 PM
> *To:* [email protected]
> *Cc:* Kevin Lew <[email protected]>
> *Subject:* Re: Looking for help
>
>
>
> You don't often get email from [email protected]. Learn why
> this is important <https://aka.ms/LearnAboutSenderIdentification>
>
> Hello Kevin,
>
>
>
> Did you update the intermediate certificate file specified in
> SSLCertificateChainFile in your httpd's config with a new one from GoDaddy?
>
>
>
> I guess that the client computer's OS simply doesn't trust GoDaddy's new
> root. AFAIK, GoDaddy began using a new root certificate
> <https://godaddy.com/help/why-is-godaddy-removing-clientauth-eku-and-transitioning-to-the-r1-root-hierarchy-for-dv-tls-issuance-42783?lc=en-US#:~:text=As%20we%20migrate%20public%20DV%20TLS%20issuance%20to%20the%20R1%20hierarchy%2C%20the%20R1%20root%20is%20still%20in%20the%20process%20of%20being%20broadly%20trusted%2Fdistributed%20in%20browser%20and%20OS%20trust%20stores.>
>  in
> 2026 and they say that it "...  is still in the process of being broadly
> trusted/distributed in browser and OS trust stores.", which essentially
> means that the root certificate isn't trusted by default by some OSes and
> web browsers.
>
>
>
> GoDaddy has an article on this topic:
> https://godaddy.com/help/fix-an-untrusted-root-or-certificate-chain-error-42951.
> The fix they suggest is to install a complete "certificate bundle" rather
> than the server certificate alone. So in addition to updating the server
> certificate, you also need to update the certificate file specified
> in SSLCertificateChainFile in your httpd's config. This will make the
> server supply the complete certificate chain to clients and will, most
> likely, resolve the issue.
>
>
>
> Note that support for SVN 1.7.x ended in 2015, so your server installation
> is quite outdated. Please plan an upgrade for your SVN server and clients.
>
>
>
> Thank you.
>
>
>
> On Thu, 19 Nov 2026 at 00:46, Kevin Lew via users <
> [email protected]> wrote:
>
> I know there are changes coming to SSL Certificates and today, I ran into
> an issue.
>
>
>
> We have a Redhat Server running svn version 1.7.14.
>
>
>
> Our GoDaddy certificate was just renewed Nov. 18, 2026.
>
> I installed the new certificate, restarted Apache as I’ve always done.
>
>
>
> The web server is fine but svn started giving our users an error that
>
>
>
> *The certificate is not issued by a trusted authority. Use the\n
> fingerprint to validate the certificate manually!\nCertificate
> information:\n –*
>
>
>
> Rolling back the certificate got svn working again.
>
>
>
> Does anyone know why this is?  I suspect it has to do with server
> authentication and client authentication no longer being on the same
> certificate, but I am not sure what needs to be done.
>
>
>
> Hopefully, there’s someone out there in the subversion community who can
> provide some insight?
>
>
>
> Thank you
>
>
>
> --
>
> With best regards,
> Pavel Lyalyakin
> VisualSVN Team
>


-- 
With best regards,
Pavel Lyalyakin
VisualSVN Team

Reply via email to