[QPIDJMS-372] [SASL] [XOAUTH2] Access token validation too restrictive

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.31.0
• Fix Version/s: 0.32.0
• Component/s: qpid-jms-client
• Assignee: Robbie Gemmell
• Reporter: Keith Wall
• Created: 26/Mar/18 11:57
• Updated: 02/Oct/19 19:22
• Resolved: 27/Mar/18 16:35

Description

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

Issue Links

• relates to: QPIDJMS-367 Add support for XOAUTH2 SASL authentication mechanism
• links to: GitHub Pull Request #16