[
https://issues.apache.org/jira/browse/QPID-7045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147573#comment-15147573
]
ASF subversion and git services commented on QPID-7045:
-------------------------------------------------------
Commit 1730565 from [~k-wall] in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1730565 ]
QPID-7028, QPID-7029, QPID-7030, QPID-7031, QPID-7045: [Java Broker/Java
Client] Add OAUTH2 authentication support for management and messaging
QPID-7055: Improve GroupProvider API
svn merge -c
1729215,1729406,1729408,1729412,1729515,1729656,1729657,1729783,1730019,1730025,1730052,1730559
^/qpid/java/trunk
> [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: [email protected]
For additional commands, e-mail: [email protected]
