[
https://issues.apache.org/jira/browse/AMQ-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13753664#comment-13753664
]
Sam Downing commented on AMQ-4693:
----------------------------------
Thanks for the pointer. The problem is how does an ActiveMQ client (both
JMS/STOMP) pass kerberos credentials to the ActiveMQ broker. I don't see any
customized headers/fields in the connect/handshake call that clients can use to
pass the kerberos credential/token. Clients also don't have access to the
socket created by ActiveMQ library, so kerberos credentials cannot be written
directly on the socket.
Also, since ActiveMQ has its connect/handshake own protocol and message
formats, how would client's kerberos credentials be passed to broker while
activemq is doing its down protocol -- this seems complicated to overlap the
two. Also the other way around, how would the broker authenticate itself to the
clients?
-Sam
> Add kerberos authentcation for TCP connectors
> ---------------------------------------------
>
> Key: AMQ-4693
> URL: https://issues.apache.org/jira/browse/AMQ-4693
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Affects Versions: 5.8.0
> Environment: linux, solaris
> Reporter: Bhanu
> Priority: Minor
>
> Hi,
> Can kerberos based authentication be added to ActiveMQ's TCP connectors.
> Thanks,
> Bhanu
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
