[
https://issues.apache.org/jira/browse/ARTEMIS-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully closed ARTEMIS-1968.
-------------------------------
Resolution: Won't Do
The amqp kerberos support sits under SASL, I don' see us adding SASL to STOMP
or Openwire for this use case.
Things like JWT tokens can already be provided over mtls in the password field
for all transports/protocols and that is a viable path forward to externalise
auth and have simple expiry/rotations.
An alternative is plain mtls for identity with JAAS cert login nodule.
> Kerberos authentication/authorization support for STOMP and Openwire
> transports
> -------------------------------------------------------------------------------
>
> Key: ARTEMIS-1968
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1968
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: OpenWire, STOMP
> Affects Versions: 2.6.2
> Reporter: Abhi
> Priority: Major
>
> I am looking to setup Artemis for my use-cases that are currently using
> ActiveMQ v5.14.1 and want to use Kerberos auth which isn't available in
> ActiveMQ currently. In Artemis, currently only AMQP transport supports
> Kerberos auth.
> Please add Kerberos auth to STOMP and Openwire.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
