[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 I don't think we should be using `sub_id`, even though it can support complex types since that should be reserved for any user information. This purely going to store the `id` for the assertion or the `jti` for the token. One alternate proposal would be to use `ext_id` as a complex type, like below: ``` "ext_id": { "format": "complex", "session": { "format": "opaque", "id": "abc123" }, "assertion": { "format": "opaque", "id": "xyz356" } } ``` Otherwise, we should probably consider the additional claim.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20260813/360ed990/attachment.htm>