[
https://issues.apache.org/jira/browse/JCR-4536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151234#comment-17151234
]
Konrad Windszus commented on JCR-4536:
--------------------------------------
My use case is FileVault RCP (https://jackrabbit.apache.org/filevault/rcp.html)
for content backstaging from one AEM instance operated by Adobe Managed
Services to another instance. The AMS instance is reachable through IP only via
TLS and has a self-signed certificate.
Therefore just hardcoding localhost for hostname verification does not work!
bq. For proposals how to restrict this, see
<https://issues.apache.org/jira/browse/JCR-4536?focusedCommentId=17055667&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17055667>.
Can you be more specific? As outlined above, I need to contact a remote
instance via IP and the self-signed cert has a non matching common name.
> Feature/enable insecure https host
> ----------------------------------
>
> Key: JCR-4536
> URL: https://issues.apache.org/jira/browse/JCR-4536
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-spi2dav
> Reporter: Max Barrass
> Assignee: Konrad Windszus
> Priority: Major
>
> Adding support for insecure parameter to allow access to https with invalid
> certs.
> Enabling optional support for expired ssl certs when using https on
> development server with self generated certificates.
> Pull request already created and ready for review
> [https://github.com/apache/jackrabbit/pull/88]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
