You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oltu.apache.org by "Jose Marcos Gomes (JIRA)" <ji...@apache.org> on 2017/01/09 16:03:58 UTC

[jira] [Created] (OLTU-205) JSON token response incorrect, google token has a unexpected format

Jose Marcos Gomes created OLTU-205:
--------------------------------------

             Summary: JSON token response incorrect, google token has a unexpected format
                 Key: OLTU-205
                 URL: https://issues.apache.org/jira/browse/OLTU-205
             Project: Apache Oltu
          Issue Type: Bug
          Components: demo-client, oauth2-common
    Affects Versions: oauth2-1.0.2
         Environment: Mac OS X 10.12.2, java 1.8.0_74, maven 3.3.9, tomcat 9
            Reporter: Jose Marcos Gomes


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?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)