[
https://issues.apache.org/jira/browse/ARTEMIS-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409365#comment-16409365
]
ASF GitHub Bot commented on ARTEMIS-1758:
-----------------------------------------
Github user gtully commented on the issue:
https://github.com/apache/activemq-artemis/pull/1961
Thanks Tim, artemis will treat the key/trust-store string as a url first
and then revert to file.
qpid-jms expects a file only. I found some certs that work among the
existing resources in the integrations tests. Also added a sanity check of the
outbound support.
also learned the need for -DskipIntegrationTests=false!
> Support SASL EXTERNAL
> ---------------------
>
> Key: ARTEMIS-1758
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1758
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: AMQP
> Affects Versions: 2.5.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 2.6.0
>
>
> Add support for SASL EXTERNAL
> https://tools.ietf.org/html/rfc4422#appendix-A
> Peer principal from TLS client cert is used as the client identity on the
> broker.
> The identity is mapped to a broker user and role via the
> TextFileCertificateLoginModule
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
