[
https://issues.apache.org/jira/browse/ARTEMIS-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-5341:
--------------------------------
Description:
SSLSupport will load the pem provider when there are pem keystores in play,
which sorts the core client.
With the artemis producer/consumer cmd line tools, there is the option to use
--protocol amqp which uses the qpid jms client. This does not use SSLSupport,
and in that case the pem provider needs to configured separately. In code or
thought java.security
it would be great if for example, the ConnectionAbstract class could parse the
brokerUrl to identify a pem store, presence of property matching
{{transport.*Store=PEM*}} and do the auto load of the provider.
This would keep pem support consistent between the supported clients.
was:
SSLSupport will load the pem provider when there are pem keystores in play,
which sorts the core client.
With the artemis producer/consumer cmd line tools, there is the option to use
--protocol amqp which uses the qpid jms client. This does not use SSLSupport,
and in that case the pem provider needs to configured separately. In code or
thought java.security
it would be great if for example, the ConnectionAbstract class could parse the
brokerUrl to identify a pem store, presence of property matching
transport.*Store=PEM* and do the auto load of the provider.
This would keep pem support consistent between the supported clients.
> Support loading pem provider for producer/consumer commands with --protocol
> amqp
> --------------------------------------------------------------------------------
>
> Key: ARTEMIS-5341
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5341
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.39.0
> Reporter: Gary Tully
> Priority: Major
>
> SSLSupport will load the pem provider when there are pem keystores in play,
> which sorts the core client.
> With the artemis producer/consumer cmd line tools, there is the option to use
> --protocol amqp which uses the qpid jms client. This does not use SSLSupport,
> and in that case the pem provider needs to configured separately. In code or
> thought java.security
> it would be great if for example, the ConnectionAbstract class could parse
> the brokerUrl to identify a pem store, presence of property matching
> {{transport.*Store=PEM*}} and do the auto load of the provider.
> This would keep pem support consistent between the supported clients.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
