oltu-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Sanso (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OLTU-205) JSON token response incorrect, google token has a unexpected format
Date Wed, 25 Oct 2017 14:46:00 GMT

     [ https://issues.apache.org/jira/browse/OLTU-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Antonio Sanso resolved OLTU-205.
--------------------------------
    Resolution: Fixed

fixed in r1813303

> 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
>            Assignee: Antonio Sanso
>              Labels: newbie, review, test
>
> 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.4.14#64029)

Mime
View raw message