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

[github at oidf.org]

openid/sharedsignals event

Issue Comment created on issue 224
Issue Title: `events_supported` field added to .well-known/ssf-configuration response
https://github.com/openid/sharedsignals/issues/224

Comment: I spent some time thinking about it, and I think I’ve come up with a possible scenario in which having `events_supported` in the TransmitterConfig instead of the StreamConfig would be useful: Imagine a future where SSF has achieved wide adoption. CompanyA has a receiver implementation and one of their customers wants to set up a stream between one of that customer's security tools (CompanyB) and CompanyA. They need to plug in the well-known, their credentials, etc. At the same time, they also need to set up routing rules for what happens for each event type. I imagine it would be useful for CompanyA to be able to list only those event types that CompanyB can send in the UI when the customer is setting all this up. If we make this change, we should deprecate the use of `events_supported` in the StreamConfig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20250124/358bc6f8/attachment.htm>