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

[github at oidf.org]

openid/sharedsignals event

Issue opened
Issue Title: Well Known Configuration for Receivers
https://github.com/openid/sharedsignals/issues/298

We have well-defined configuration metadata for transmitters : https://openid.net/specs/openid-sharedsignals-framework-1_0.html#name-obtaining-transmitter-confi But nothing equivalent exist for receivers. There are few usecases for this : 1. Non-existence of such config somewhat forces integration to begin on receiving partner. In a truly interoperable world, transmitting partners could also "discover" new receiver and metadata about it and configure a stream on behalf of receiver. 2. Even when integration starts on receiving partner end, transmitter may want to use some public data about the receiver (e.g, public part of cryptographic key) to verify that the stream creation API was truly invoked by the well known receiver. Some useful things that we might want to put in receiver data : 1. Auth protocols (potentially public keys ?) 2. Endpoint URL to where transmitters can send new stream configs to in case they create a stream on-behalf-of receiver. 3. Data transmitter can use to create credentials on behalf of receiver for future pulls or stream management
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20251007/4af644e1/attachment.htm>