I reported the same issue for Apache Sling already in
https://issues.apache.org/jira/browse/INFRA-13980. Feel free to vote/watch.
The certificate has been updated recently and it seems the CA is not (yet) in
all trust stores.
Konrad
> On 24. Apr 2017, at 14:47, dav...@apache.org wrote:
>
> Hi infra,
>
> When I update the Felix CMS using the 'Update' link on the page I'm getting
> the following message on the web page:
>
> "Update complete
>
> Status
>
> Updating 'usr/local/cms/wc/felix/davidb-NVWGRt/trunk':
> Error validating server certificate for 'https://svn.apache.org:443':
> - The certificate is not issued by a trusted authority. Use the
> fingerprint to validate the certificate manually!
> Certificate information:
> - Hostname: *.apache.org
> - Valid: from Fri, 21 Apr 2017 00:00:00 GMT until Sat, 20 Jul 2019
> 23:59:59 GMT
> - Issuer: www.ssl.com, SSL.com, US
> - Fingerprint: 2d:97:67:d9:2e:20:ee:07:3d:26:da:97:a6:43:36:5f:71:8e:94:19
> (R)eject, accept (t)emporarily or accept (p)ermanently? svn: E175002:
> Unable to connect to a repository at URL '
> https://svn.apache.org/repos/asf/felix/site'
> svn: E175002: OPTIONS of 'https://svn.apache.org/repos/asf/felix/site':
> Server certificate verification failed: issuer is not trusted (
> https://svn.apache.org)
> [Edit] [Browse] [Diff]"
>
> I'm not sure what happened, maybe the SSL cert was updated or something. I
> also get this locally, but there I can simply accept this by responding.
> Does anyone know how we can do this in the CMS given that there is no way
> to anwer with 'R, t or p' to the question?
>
> Thanks!
>
> David
