[jira] [Updated] (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:all-tabpanel ] Julian Reschke updated JCR-4574: Labels: (was: candidate_jcr_2_16) > 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 > Fix For: 2.22, 2.20.2, 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)
[jira] [Updated] (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:all-tabpanel ] Julian Reschke updated JCR-4574: Labels: candidate_jcr_2_18 (was: candidate_jcr_2_20) > 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_18 > Fix For: 2.22, 2.20.2, 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)
[jira] [Updated] (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:all-tabpanel ] Julian Reschke updated JCR-4574: Fix Version/s: 2.20.2 > 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.20.2, 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)
[jira] [Updated] (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:all-tabpanel ] Julian Reschke updated JCR-4574: Labels: candidate_jcr_2_20 (was: ) > 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)
[jira] [Updated] (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:all-tabpanel ] Julian Reschke updated JCR-4574: Summary: add tests for https (with self-signed cert) (was: add tests for https) > 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 > 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)
[jira] [Updated] (JCR-4574) add tests for https
[ https://issues.apache.org/jira/browse/JCR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4574: Attachment: https2.diff > add tests for https > --- > > 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 > 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)
[jira] [Updated] (JCR-4574) add tests for https
[ https://issues.apache.org/jira/browse/JCR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4574: Attachment: keystore > add tests for https > --- > > 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 >Priority: Minor > Attachments: https.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)
[jira] [Updated] (JCR-4574) add tests for https
[ https://issues.apache.org/jira/browse/JCR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4574: Attachment: https.diff > add tests for https > --- > > 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 >Priority: Minor > Attachments: https.diff > > > 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)
[jira] [Updated] (JCR-4574) add tests for https
[ https://issues.apache.org/jira/browse/JCR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4574: Attachment: (was: https.diff) > add tests for https > --- > > 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 >Priority: Minor > > 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)
[jira] [Updated] (JCR-4574) add tests for https
[ https://issues.apache.org/jira/browse/JCR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4574: Attachment: (was: https.diff) > add tests for https > --- > > 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 >Priority: Minor > Attachments: https.diff > > > 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)
[jira] [Updated] (JCR-4574) add tests for https
[ https://issues.apache.org/jira/browse/JCR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4574: Attachment: https.diff > add tests for https > --- > > 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 >Priority: Minor > Attachments: https.diff > > > 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)
[jira] [Updated] (JCR-4574) add tests for https
[ https://issues.apache.org/jira/browse/JCR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4574: Attachment: (was: https.diff) > add tests for https > --- > > 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 >Priority: Minor > Attachments: https.diff > > > 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)
[jira] [Updated] (JCR-4574) add tests for https
[ https://issues.apache.org/jira/browse/JCR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4574: Attachment: https.diff > add tests for https > --- > > 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 >Priority: Minor > Attachments: https.diff > > > 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)
[jira] [Updated] (JCR-4574) add tests for https
[ https://issues.apache.org/jira/browse/JCR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4574: Attachment: (was: https.diff) > add tests for https > --- > > 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 >Priority: Minor > Attachments: https.diff > > > 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)
[jira] [Updated] (JCR-4574) add tests for https
[ https://issues.apache.org/jira/browse/JCR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4574: Attachment: https.diff > add tests for https > --- > > 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 >Priority: Minor > Attachments: https.diff > > > 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)
[jira] [Updated] (JCR-4574) add tests for https
[ https://issues.apache.org/jira/browse/JCR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4574: Attachment: https.diff > add tests for https > --- > > 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 >Priority: Minor > Attachments: https.diff > > > 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)
