qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-8178) [Broker-J] [Websocket] Support authentication from bearer token carried by authentication header
Date Wed, 02 May 2018 12:57:00 GMT

    [ https://issues.apache.org/jira/browse/QPID-8178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460986#comment-16460986

Keith Wall commented on QPID-8178:

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
> ------------------------------------------------------------------------------------------------
>                 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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message