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

[github at oidf.org]

openid/sharedsignals event

Issue Comment created on issue 348
Issue Title: Consider adding a unique token identifier to Session Established CAEP Events
https://github.com/openid/sharedsignals/issues/348

Comment: @appsdesh If we use `sub_id`, even though it can support complex types for user and session, that could be misleading since this is purely going to store the `id` for the assertion or the `jti` for the token and is not a principal subject of the event. One alternate proposal would be to use `ext_id` as a complex type to store such additional context wherever necessary, like below: ```"ext_id": { "format": "complex", "session": { "format": "opaque", "id": "abc123" }, "assertion": { "format": "opaque", "id": "xyz356" } } ``` Thoughts?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20260813/4bae8c3e/attachment-0001.htm>