qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7045) [Java Broker] Add OAuth2 SASL mechanism
Date Mon, 08 Feb 2016 17:30:40 GMT

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

ASF subversion and git services commented on QPID-7045:
-------------------------------------------------------

Commit 1729215 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1729215 ]

QPID-7028, QPID-7029, QPID-7030, QPID-7031, QPID-7045: [Java Broker/Java Client] Add OAUTH2
authentication support for management and messaging

* Includes integration with Google and CloudFoundry OAuth2 backends

> [Java Broker] Add OAuth2 SASL mechanism
> ---------------------------------------
>
>                 Key: QPID-7045
>                 URL: https://issues.apache.org/jira/browse/QPID-7045
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker
>            Reporter: Lorenz Quack
>         Attachments: 0001-QPID-7045-Java-Broker-Java-Client-Add-XOAUTH2-implem.patch
>
>
> We want a OAuth2 SASL mechanism.
> There seem to be at least 2 popular implementations in the wild:
>  * [Googles OAuth2 mechanism|https://developers.google.com/gmail/xoauth2_protocol?hl=en]
>  * [IETF Draft|https://tools.ietf.org/html/draft-ietf-kitten-sasl-oauth-23]
> Our implementation should accommodate for these different options. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message