We should probably update the events to include the description or add some
debug logging. I'd say updating events is probably the ideal approach.
Would need changes in Keycloak though.
On 27 November 2017 at 17:57, Jared Blashka <jblashka(a)redhat.com> wrote:
Some of our clients are generating many REFRESH_TOKEN_ERROR events
but I
don't see anywhere that the error description from the exception is
logged/stored. The keycloak event itself only says 'invalid token', but I'd
like to see the
'{"error":"invalid_grant","error_description":"Session
not
active"}' details as well to be able to provide specific guidance around
why their refresh calls are failing.
I tried registering an Exception Mapper provider, but it doesn't looks like
that's supported yet (
http://lists.jboss.org/pipermail/keycloak-dev/2016-June/007361.html).
We're running RH-SSO 7.1.3.
Thanks!
Jared Blashka
Red Hat
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev