[jira] [Commented] (KARAF-4882) keystore.jks update in karaf requires force restart

["Suresh Perumal (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KARAF-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15727776#comment-15727776 ] 

Suresh Perumal commented on KARAF-4882:
---------------------------------------

Below is the content used in pax-web.
We are creating keystore.jks with java keytool command
We use this key - self signed certificate during https acess.
org.ops4j.pax.web.cfg
org.osgi.service.http.port=8181
org.osgi.service.http.port.secure=8443
org.osgi.service.http.secure.enabled=true
org.ops4j.pax.web.ssl.keystore=/opt/vira/fpm4.1/karaf/etc/keystores/keystore.jks
org.ops4j.pax.web.ssl.password=password
org.ops4j.pax.web.ssl.keypassword=password
org.ops4j.pax.web.config.file=/opt/vira/fpm4.1/karaf/etc/jetty.xml


> keystore.jks update in karaf requires force restart
> ---------------------------------------------------
>
>                 Key: KARAF-4882
>                 URL: https://issues.apache.org/jira/browse/KARAF-4882
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 4.0.5
>         Environment: Cent OS 7.2, RHEL 7.2
>            Reporter: Suresh Perumal
>            Priority: Blocker
>
> We are using Karaf 4.0.5, 4.0.6.
> We are using self signed certificate for https support.
> There are some scenarios where the certificate will get expired where we need to regenerate the certificate again.
> During this scenario, newly generated keystore.jks getting stored in Karaf. ,KARAF_HOME/etc folder.
> But looks like it is not picking up the latest keystore.jks and it requires restart of karaf server.
> To some extent we will not be able to restart the karaf server which might not be correct approach.
> I would like to know the approach to force update of certificates without restarts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)