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

[github at oidf.org]

openid/sharedsignals event

Issue Comment created on issue 351
Issue Title: CAEP Interop Profile: Event Subjects section does not permit Complex Subjects
https://github.com/openid/sharedsignals/issues/351

Comment: The emulated receiver used by the SSF Transmitter conformance tests will accept any subject listed in https://openid.github.io/sharedsignals/openid-caep-interoperability-profile-1_0.html#section-2.5. The current implementation warns if a subject with complex format is observed. I'll update the emulated transmitter used by the SSF Receiver conformance tests to emit dedicated events for the "events_delived" for each example subject provided in the `ssf.subjects.valid` array in the test configuration For example, for a `ssf.subjects.valid` configuration with three subject formats as shown below and two events_delivered: {session-revoked, credentials-changed}: ```json [ { "format": "email", "email": "foo at example.com" }, { "format": "iss_sub", "iss": "https://idp.example.com", "sub": "1234" }, { "format": "complex", "user": { "format": "email", "email": "bar at example.com" }, "tenant": { "format": "iss_sub", "iss": "https://example.com/idp1", "sub": "1234" } } ] ``` we will emit six events in total. Note that we will generate a warning if we observe subject format "complex" being used. Once the subject type complex is officially allowed by the CAEP interop profile, we will remove the warning from the conformance tests.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20260825/5212f70b/attachment-0001.htm>