It's trying to invoke a deprecated endpoint. This should already be fixed.

On 13 Apr 2016 19:03, "Sebastien Blanc" <sblanc@redhat.com> wrote:
I don't think so , stack trace sounds more like an old school wildly error ;)

Le mercredi 13 avril 2016, Luke Holmquist <lholmqui@redhat.com> a écrit :
seb,

is it because of this?  https://issues.jboss.org/browse/KEYCLOAK-2798

On Wed, Apr 13, 2016 at 12:52 PM, Sebastien Blanc <sblanc@redhat.com> wrote:
Hi,

I'm trying the nodejs example provided here https://github.com/sebastienblanc/keycloak-nodejs-connect/tree/master/example and using Keycloak 1.9.1.Final.

Once the nodejs app launched I am corectly redirected to the login page. But once I log in I can see a stacktrace in KC : https://gist.github.com/sebastienblanc/337597c8e570e5267c26f30b93c3c804 and the nodejs app hangs.

Is it because of KC version, should I try with KC master ?

Thx,

Sebi


_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user


_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user