[OLTU-205] JSON token response incorrect, google token has a unexpected format

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: oauth2-1.0.2
• Fix Version/s: openidconnect-client-0.0.1
• Component/s: demo-client, oauth2-common
• Labels: newbie review test
• Environment: Mac OS X 10.12.2, java 1.8.0_74, maven 3.3.9, tomcat 9
• Assignee: Antonio Sanso
• Reporter: Jose Marcos Gomes
• Created: 09/Jan/17 16:02
• Updated: 25/Oct/17 14:45
• Resolved: 25/Oct/17 14:45

Description

Testing Google integration using the OLTU demo app, the first problem was the response JSON payload, where Google use "access_token" while org.apache.oltu.openidconnect.client.response.OpenIdConnectResponse.init expects ==>OpenIdConnect.ID_TOKEN (= 'id_token');

After that comes the token, and the token does not came as expected in org.apache.oltu.commons.encodedtoken.TokenReader pattern (the group 3 part (signature?) is missing! Can this be a problem from Google or I misconfigured something?