[
https://issues.apache.org/jira/browse/QPID-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460986#comment-16460986
]
Keith Wall edited comment on QPID-8178 at 5/2/18 12:57 PM:
-----------------------------------------------------------
Yes, for the SASL case, I think presenting a EXTERNAL SASL is the appropriate
choice. I admit that I had rather conflated SASL EXTERNAL with SSL client
auth, but having read the spec [1], I see that its use in this case would be an
appropriate choice.
[1] https://tools.ietf.org/html/rfc4422#page-29
was (Author: k-wall):
Yes, for the SASL case, I think presenting a EXTERNAL SASL is the appropriate
choice. I admit that I had rather conflated SASL EXTERNAL with SSL client
auth, but having read the spec, I see that its use in this case would be an
appropriate choice.
> [Broker-J] [Websocket] Support authentication from bearer token carried by
> authentication header
> ------------------------------------------------------------------------------------------------
>
> Key: QPID-8178
> URL: https://issues.apache.org/jira/browse/QPID-8178
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Reporter: Keith Wall
> Priority: Minor
> Fix For: Future
>
>
> Broker-J's AMQP websocket support should be enhanced to accept a bearer token
> from the websocket transport. If present and the port is configured to use
> an authentication provider that supports the XOAUTH-2 mechanism, the token
> should be passed to the authentication provider so it can complete the
> authentication process.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
