Overview
The post-login Action offers two parameters that we can use: the “event”(Actions Triggers: post-login—Event Object) and the “API”(Actions Triggers: post-login—API Object) objects. In this scenario, the event object has additional details regarding the session object.
It can be difficult to understand the difference between the session object’s properties, so this article will provide a better explanation and the differences for the following:
- event.session.authenticated_at
- event.session.created_at
- event.session.last_interacted_at
- event.session.update_at
Applies To
- Actions
- Event Objects
- Post-login Actions
Solution
- event.session.authenticated_at: The last time the user authenticated with the session
- event.session.created_at: When the session has been established, or in other words, when the user first authenticated
- event.session.last_interacted_at: The last successful user interaction with the session (e.g. silent authentication)
- event.session.updated_at: The last interaction of any kind (including failed interactions) within the session
Some additional notes:
authenticated_at and created_at typically are the same because the session is established exactly after the first user authentication. However, authenticated_at can differ later on. While last_interacted_at and updated_at might occasionally align, updated_at is updated for any interaction (including failures).