[
https://issues.apache.org/jira/browse/JCR-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561361#comment-17561361
]
Konrad Windszus commented on JCR-4799:
--------------------------------------
Maybe one can add an (integration) test for
https://github.com/apache/jackrabbit/blob/trunk/jackrabbit-spi2dav/src/main/java/org/apache/jackrabbit/spi2dav/RepositoryServiceImpl.java
which does a simple HTTPS GET on an existing server with a valid cert (trusted
by all relevant JREs), like https://jackrabbit.apache.org/jcr/index.html
(completely independent of
https://jackrabbit.apache.org/jcr/JCR_Webdav_Protocol.doc) leveraging the
underlying HTTP client.
> jackrabbit.client.useSystemProperties undone by SSL config: client
> certificates no longer work
> ----------------------------------------------------------------------------------------------
>
> Key: JCR-4799
> URL: https://issues.apache.org/jira/browse/JCR-4799
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-spi2dav
> Affects Versions: 2.20.5
> Reporter: Graham Leggett
> Assignee: Julian Reschke
> Priority: Major
> Fix For: 2.22
>
> Attachments: jackrabbit-spi2dav-system.patch
>
>
> When jackrabbit.client.useSystemProperties is used in an effort to make
> java.net.ssl.* constants work, this is undone by the explicit initialisation
> of SSL.
> As a result, client certificates no longer work, and control over SSL
> parameters like protocol, etc is lost.
> The fix is to use the SSLConnectionSocketFactory.getSystemSocketFactory()
> constructor in the system properties case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
