[Openid-specs-risc] openid/sharedsignals: Comment created on issue 221

[github at oidf.org]

openid/sharedsignals event

Issue Comment created on issue 221
Issue Title: Addition of Event data field inside events
https://github.com/openid/sharedsignals/issues/221

Comment: @jischr I think that's correct. We should update the CAEP and RISC specs, not the SSF spec. If we wanted to limit this change to the SSF spec, we could potentially create a field that lives at the same level as `events` to hold this information, but that feels a bit gross to me. It would look like this ``` { "iss": "https://idp.example.com/", "jti": "756E69717565206964656E746966696572", "iat": 1520364019, "txn": 8675309, "aud": "636C69656E745F6964", "sub_id": { "format": "email", "email": "user at example.com" }, "events": { "https://schemas.openid.net/secevent/caep/event-type/token-claims-change": { "claims": { "token": "some-token-value" } } }, "event_data": { "https://schemas.openid.net/secevent/caep/event-type/token-claims-change": { "something":"foo", "blah":"bar", "blah2":"example2" } } } ```
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20250325/27f30d86/attachment.htm>