felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.W. Janssen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-1955) Possibility to configure keystore type (Currently only JKS is available)
Date Mon, 11 Nov 2013 13:58:17 GMT

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

J.W. Janssen resolved FELIX-1955.

    Resolution: Fixed
      Assignee: J.W. Janssen

Committed support for this in rev #1540723 and added two new configuration options {{org.apache.felix.https.keystore.type}}
 and {{org.apache.felix.https.truststore.type}} to define what type of store is to be expected.

Local tests with a PKCS12 store work as expected.

> Possibility to configure keystore type (Currently only JKS is available)
> ------------------------------------------------------------------------
>                 Key: FELIX-1955
>                 URL: https://issues.apache.org/jira/browse/FELIX-1955
>             Project: Felix
>          Issue Type: Improvement
>          Components: HTTP Service
>    Affects Versions: http-2.0.4
>            Reporter: Boris Toninski
>            Assignee: J.W. Janssen
> There should be a way to configure the keystore type to be used for SSL comunication.
Currently as I can see "JKS" is used as default in org.mortbay.jetty.security.SslSocketConnector.
> The problem with this is that there are classpath implementations that do not support
JKS keystore algorithm.  We develop a project which runs on such classpath and this is a real
stopper for us.

This message was sent by Atlassian JIRA

View raw message