[
https://issues.apache.org/jira/browse/QPID-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460636#comment-16460636
]
Keith Wall edited comment on QPID-8178 at 5/2/18 7:44 AM:
----------------------------------------------------------
It could work in a similar way to the non-SASL external authentication
(org.apache.qpid.server.protocol.v1_0.AMQPConnection_1_0Impl#processProtocolHeader).
In this case, the transport would provide the token rather than a peer
principal.
was (Author: k-wall):
It could work in a similar way to the external authentication
(org.apache.qpid.server.protocol.v1_0.AMQPConnection_1_0Impl#processProtocolHeader).
In this case, the transport would provide the token rather than a peer
principal.
> [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]
