Re: [keycloak-user] Direct Connect API call results in JWT with missing idtoken?
Please check the migration guide before upgrading
https://keycloak.gitbooks.io/documentation/server_admin/topics/MigrationF...
You need to add scope=openid otherwise the ID token won't be returned and
it will be counted as an OAuth2 request rather than an OpenID Connect
request.
On 6 July 2017 at 05:27, Thomas Connolly <thomas_connolly(a)yahoo.com> wrote:
Hi All
I've just raised the following ticket for a potential bug in KC
3.2.0.Final and KC 3.2.0.CR1.
https://issues.jboss.org/browse/KEYCLOAK-5145
I'd really appreciate if you could determine if I've missed something or
there is an actual bug.
As per bug description using an unconfigured KC.
Regards
Tom Connolly.
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user