[Openid-specs-risc] openid/sharedsignals: New Issue opened

[github at oidf.org]

openid/sharedsignals event

Issue opened
Issue Title: txn claim example values should be strings
https://github.com/openid/sharedsignals/issues/273

The SSF specification includes `txn` claim example values like below. Their values are integers. ```json { "jti": "123456", "iss": "https://transmitter.example.com", "aud": ["receiver.example.com/web", "receiver.example.com/mobile"], "iat": 1493856000, "txn": 8675309, "sub_id": { "format": "opaque", "id": "72e6991badb44e08a69672960053b342" }, "events": { "https://schemas.openid.net/secevent/ssf/event-type/verification": { "state": "VGhpcyBpcyBhbiBleGFtcGxlIHN0YXRlIHZhbHVlLgo=" } } } ``` However, since [Section 2.2. Core SET Claims](https://www.rfc-editor.org/rfc/rfc8417.html#section-2.2) of [RFC 8417: Security Event Token (SET)](https://www.rfc-editor.org/rfc/rfc8417.html), a family spec of SSF, explains the `txn` claim as _"An OPTIONAL **string** value"_ as below: >"txn" (Transaction Identifier) Claim > >An OPTIONAL **string** value that represents a unique transaction identifier. In cases in which multiple related JWTs are issued, the transaction identifier claim can be used to correlate these related JWTs. Note that this claim can be used in JWTs that are SETs and also in JWTs using non-SET profiles. `txn` claim example values in the SSF specification should be changed from integers to strings.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20250622/f594fe74/attachment.htm>