Repository navigation
Send event after SSO Session Idle time runs out #44689
Replies: 2 comments 1 reply
|
I think this feature is achievable using workflows, which is a new feature in 26.4 as described in #43171. I think workflows are the only way to check for events dynamically (@sguilhen or @pedroigor could correct me on this). Otherwise the session idle timeout can be checked on user activity, as it doesn't really affect the system otherwise. Consequently, the event is unlikely to be sent in any reasonably timely manner (it would be sent on the next user activity and since it's an idle timeout event, it's unlikely it would be triggered by active users). |
|
We have now an event that is fired when a session is destroyed by the background task that removes expired sessions, but we need to make it also work on other places that cause a session to be terminated (See #44564) There might be a delay between the exact time the session times out, and the time the task runs to destroy the sessions, so any workflow triggered by this event will not activate exactly at the time the session times out, but in a reasonable amount of time after that. I don't recall atm how frequently the task runs, @ahus1 might be able to give a more precise answer. |
|
There is a new event The event is currently triggered at the earliest 3 minutes after the session has timed out, and the job runs every 3 minutes by default. Assuming that the job keeps up with deleting the sessions, you should get the event within 10 minutes. Note that we still don't trigger any backchannel logouts for timed out sessions. We might reduce that delay in future releases, and might also consider triggering the backchannel logouts. If you have good use cases this is important, let us know. |
Uh oh!
There was an error while loading. Please reload this page.
Create or send an onAuthLogout event when SSO Session Idle time runs out
All reactions