Can't really tell, but maybe your library doesn't like the token format
we send back? Just looking at the 1st exception in the log...
Log a jira and we can look into it. Our queue is pretty full at the
On 10/20/2014 11:28 AM, Iván Perdomo wrote:
On Thu, 25 Sep 2014 14:53:04 +0200
Iván Perdomo <ivan(a)akvo.org> wrote:
> I'll do some testing using third-party libs/clients and will share my
I'm testing a simple OIDC Android app  and Keycloack (1.0.1.Final)
Some minor configuration settings are required on this sample app :
authorizationServerUrl = https://host/auth/name/rname/tokens/login
tokenServerUrl = https://host/auth/realms/name/tokens/access/codes
userInfoUrl = https://host/auth/realms/name/account
After making a build and test in in my mobile, I'm able to:
* get redirected to the login
* Successfully login
* get redirected to the grant options
After granting access to the application, I should get a new account on
my mobile, but I'm getting an exception: "Invalid ID token returned" 
The whole adb logcat log is a bit verbose, but you can see the
java.io.IOException: Invalid ID token returned.
com.google.api.client.auth.oauth2.TokenResponseException: 400 Bad
"error_description": "Code not found"
I can discard the idea of a bug in the sample code because I managed to
successfully login using Mitre's Open ID connect Spring implementation
Any ideas how to know what's going wrong? I would love to get
Keycloak and this sample code working.
Thanks for your support.
JBoss, a division of Red Hat