Skip to content

For Issue 281 - Clarification on Session Presented and Session Established CAEP events. #283

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
iamseanodentity wants to merge 1 commit into
base: main
Choose a base branch
from
Open

For Issue 281 - Clarification on Session Presented and Session Established CAEP events. #283

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions openid-caep-1_0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -785,9 +785,9 @@ new session for the subject. Receivers may use this information for a number of
reasons, including:

* A service acting as a Transmitter can close the loop with the IdP after a user
has been federated from the IdP
* An IdP can detect unintended logins
* A Receiver can establish an inventory of user sessions
has been federated from the IdP. Specifically, A confirmation from an application or system, the SP, to the identity provider, IdP, that a session in the application or system has been created based on an assertion from the IdP. This could act as a reconcile event to "close the loop" with an originating "session presented" event.
* An IdP can detect unintended logins.
* A Receiver can establish an inventory of user sessions.

The `event_timestamp` in this event type specifies the time at which the session
was established.
Expand Down Expand Up @@ -854,10 +854,10 @@ Event Type URI:

The Session Presented event signifies that the Transmitter has observed the
session to be present at the Transmitter at the time indicated by the
`event_timestamp` field in the Session Presented event. Receivers may use this
`event_timestamp` field in the Session Presented event. A presciptive example here would be for SSO activity or events from an IdP, meaning there is an already established SSO session. This event could be used in conjuction with a "session established" event for reconciliation purposes. Receivers may use this
information for reasons that include:

* Detecting abnormal user activity
* Detecting abnormal user activity, such as lateral movement
* Establishing an inventory of live sessions belonging to a user

### Event Specific Claims {#session-presented-event-specific-claims}
Expand Down