[
https://issues.apache.org/jira/browse/ARTEMIS-4528?focusedWorklogId=894399&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-894399
]
ASF GitHub Bot logged work on ARTEMIS-4528:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Dec/23 22:34
Start Date: 06/Dec/23 22:34
Worklog Time Spent: 10m
Work Description: tabish121 commented on PR #4706:
URL:
https://github.com/apache/activemq-artemis/pull/4706#issuecomment-1843796721
> This looks great overall, but I have one question. Why did so many
(seemingly) unrelated SSL resources change (e.g. keystores, truststores, etc.)?
My guess was the changes in the security resources 'build.sh' to create the
needed certs resulted in a rerun of the script which updated all the
certificates it creates.
Issue Time Tracking
-------------------
Worklog Id: (was: 894399)
Time Spent: 0.5h (was: 20m)
> TLS support PEM format for key and trust store type
> ---------------------------------------------------
>
> Key: ARTEMIS-4528
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4528
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 2.31.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 2.32.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> managing key and trust store passwords when the credentials are securely
> stored or managed by other means is a nuisance.
> there is a nice PEM keystore provider at:
> [https://github.com/ctron/pem-keystore]
> This gives us an intuitive way to easily reference a simple cert or key
> without a password as is the case with jsk or pkcs12
> <acceptor
> name="netty-ssl-acceptor">tcp://localhost:5500?sslEnabled=true;keyStorePath=server-keystore.pem;keyStoreType=PEM</acceptor>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
