[
https://issues.apache.org/jira/browse/QPIDJMS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415887#comment-16415887
]
ASF subversion and git services commented on QPIDJMS-372:
---------------------------------------------------------
Commit dfc24eeab7f34ad54d3b64201d7a8034802b847b in qpid-jms's branch
refs/heads/master from [~k-wall]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=dfc24ee ]
QPIDJMS-372: [SASL] [XOAUTH2] Make access token validation comply with RFC-6749.
> [SASL] [XOAUTH2] Access token validation too restrictive
> --------------------------------------------------------
>
> Key: QPIDJMS-372
> URL: https://issues.apache.org/jira/browse/QPIDJMS-372
> Project: Qpid JMS
> Issue Type: Bug
> Components: qpid-jms-client
> Affects Versions: 0.31.0
> Reporter: Keith Wall
> Priority: Major
>
> http://qpid.2158936.n2.nabble.com/VOTE-Release-Apache-Qpid-JMS-0-31-0-td7674038.html
> Google's access_tokens from {{/oauth2/v4/token}} use characters drawn from
> outside Base64's 64 character set. RFC 6749[1] defines an
> access_token element as within {{%x20-7E}}, so the code within
> {{org.apache.qpid.jms.sasl.XOauth2Mechanism#isApplicable}} is too
> restrictive.
> [1] https://tools.ietf.org/html/rfc6749
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
