You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/12/08 17:49:00 UTC

[jira] [Resolved] (JCRVLT-574) vlt does not properly handle connection options

     [ https://issues.apache.org/jira/browse/JCRVLT-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus resolved JCRVLT-574.
------------------------------------
    Resolution: Fixed

Fixed in https://github.com/apache/jackrabbit-filevault/commit/93c4f915d515dd053c094430389fdd90d4c808c5.

> vlt does not properly handle connection options
> -----------------------------------------------
>
>                 Key: JCRVLT-574
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-574
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: vlt
>    Affects Versions: 3.5.6
>            Reporter: Julian Reschke
>            Assignee: Konrad Windszus
>            Priority: Minor
>             Fix For: 3.5.8
>
>
> vlt has support for "{{{}--allowSelfSignedCertificates{}}}" and "{{{}--disableHostnameValidator{}}}", but when used, these options are not passed down to the instantiation of the {{{}DAVExRepositoryFactory{}}} via the {{VltContext}}.
> (see https://github.com/apache/jackrabbit-filevault/blob/21b49e58f9ece657d5c7d473a00dac494508f44a/vault-vlt/src/main/java/org/apache/jackrabbit/vault/vlt/VltContext.java#L247)
> Only {{VaultFsApp.connect()}} (https://github.com/apache/jackrabbit-filevault/blob/21b49e58f9ece657d5c7d473a00dac494508f44a/vault-cli/src/main/java/org/apache/jackrabbit/vault/cli/VaultFsApp.java#L405-L407) is considering the options right now.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)