You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Julian Reschke (Jira)" <ji...@apache.org> on 2022/06/24 09:52:00 UTC

[jira] [Commented] (JCR-4799) jackrabbit.client.useSystemProperties undone by SSL config: client certificates no longer work

    [ https://issues.apache.org/jira/browse/JCR-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558416#comment-17558416 ] 

Julian Reschke commented on JCR-4799:
-------------------------------------

[~minfrin] - I tried your patch and can confirm that it doesn't break anything covered by tests. That being said, maybe we should extend ConnectionOptionsTest to cover the new functionality?

> 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.7#820007)