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 2020/07/17 04:11:00 UTC
[jira] [Comment Edited] (JCR-4574) add tests for https (with
self-signed cert)
[ https://issues.apache.org/jira/browse/JCR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17153550#comment-17153550 ]
Julian Reschke edited comment on JCR-4574 at 7/17/20, 4:10 AM:
---------------------------------------------------------------
trunk: [r1879977|http://svn.apache.org/r1879977] [r1879647|http://svn.apache.org/r1879647]
was (Author: reschke):
trunk: [r1879647|http://svn.apache.org/r1879647]
> add tests for https (with self-signed cert)
> -------------------------------------------
>
> Key: JCR-4574
> URL: https://issues.apache.org/jira/browse/JCR-4574
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-jcr-server
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Labels: candidate_jcr_2_20
> Fix For: 2.22, 2.21.3
>
> Attachments: https.diff, https2.diff, keystore
>
>
> With JCR-4169 done, it would be good if we could start testing with https as well.
> The first step would be to verify that - if the server runs with an incorrect or self-signed certificate - the client will indeed refuse to connect.
> That would be a precondition before adding knobs to relax the cert checking, as proposed in JCR-4536-
--
This message was sent by Atlassian Jira
(v8.3.4#803005)