Skip to content
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.

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

Addition of Event data field inside events #221

Open
iamseanodentity opened this issue Nov 7, 2024 · 2 comments
Open

Addition of Event data field inside events #221

iamseanodentity opened this issue Nov 7, 2024 · 2 comments
Labels
v1Final Issues that must be fixed before we propose a spec to become a v1 final spec.

Comments

@iamseanodentity
Copy link
Contributor

iamseanodentity commented Nov 7, 2024

The intent is to be able to offer guidelines for all events in order to allow transmitters to provide more metadata that can be specific to the event and or action(s) in the event.

example:

  "events": {
    "https://schemas.openid.net/secevent/caep/event-type/session-revoked": {
      "event_timestamp": 1615304991643,
      "event_data": {
        "something":"foo",
        "blah":"bar",
        "blah2":"example2"
      }
    }
  }
@tulshi
Copy link
Contributor

tulshi commented Nov 7, 2024

This can be a change to the SSF spec, where we add recommended language about any additional data that needs to be sent in an event SHOULD be sent using the "event_data" field.

@iamseanodentity
Copy link
Contributor Author

I can start on this if you would like

@iamseanodentity iamseanodentity added the v1Final Issues that must be fixed before we propose a spec to become a v1 final spec. label Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v1Final Issues that must be fixed before we propose a spec to become a v1 final spec.
Projects
None yet
Development

No branches or pull requests

2 participants