[prev in list] [next in list] [prev in thread] [next in thread] 

List:       keycloak-user
Subject:    [keycloak-user] Custom Adapter Logout logic
From:       josh.cain () redhat ! com (Josh Cain)
Date:       2016-09-30 15:29:20
Message-ID: CA+z0A8Do7rObLDLy6MnmkiPm83+sHuAShYVBuPnno0=Pnj16Gw () mail ! gmail ! com
[Download RAW message or body]

What would you recommend for this on the IDP side?  I know we can hook into
events, but doing operations with the response in an EventListenerProvider
just feels wrong.  What's more, on the IDP side I wouldn't want to touch
the Keycloak deployment descriptors.

Josh Cain | Software Applications Engineer
*Identity and Access Management*
*Red Hat*
+1 256-452-0150

On Tue, Sep 20, 2016 at 3:00 AM, Stian Thorgersen <sthorger at redhat.com>
wrote:

> Could you use a HttpSessionListener?
>
> On 15 September 2016 at 23:16, Jared Blashka <jblashka at redhat.com> wrote:
>
>> Is it currently possible to hook into the adapter's logout logic to
>> trigger some custom behavior without interrupting the logout flow?
>>
>> For example, if I want to audit logout activity on a particular SP or
>> delete some cookies (if it was a front-channel logout request) without
>> stopping the normal federated logout process.
>>
>> Jared
>>
>> _______________________________________________
>> keycloak-user mailing list
>> keycloak-user at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-user
>>
>
>
> _______________________________________________
> keycloak-user mailing list
> keycloak-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user
>

[prev in list] [next in list] [prev in thread] [next in thread]