[
https://issues.apache.org/jira/browse/QPIDJMS-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16398668#comment-16398668
]
ASF subversion and git services commented on QPIDJMS-367:
---------------------------------------------------------
Commit 3d2ec9c5fc65d512418b21086ee6a59a00bb2df4 in qpid-jms's branch
refs/heads/master from [~godfrer]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=3d2ec9c ]
QPIDJMS-367 : Add support for XOAUTH2 Sasl Autentication
> Add support for XOAUTH2 Sasl Autentication
> ------------------------------------------
>
> Key: QPIDJMS-367
> URL: https://issues.apache.org/jira/browse/QPIDJMS-367
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Reporter: Rob Godfrey
> Priority: Major
>
> [https://developers.google.com/gmail/imap/xoauth2-protocol] defines a SASL
> mechanism which allows for authentication using an OAUTH2 Acess Token. This
> mechanism is supported by Qpid Broker-J and it would be useful if the Qpid
> JMS client could connect using this mechanism.
> The mechanics of the mechanism pass a username and token, the latter
> essentially being equivalent to a password for these purposes. The Token
> MUST be provided as a Base64 encoded string (the contents of which are a
> token in JSON format, though this detail is opaque to the client).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
