Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Added language requiring authorization of stream management API #173

Merged
merged 6 commits into from
Jun 10, 2024
Merged

Added language requiring authorization of stream management API #173

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
49f6d92
Added language requiring authorization of stream management API
FragLegs May 23, 2024
c4d6eb2
Remove sentence referring the reader to where authorization scheme ca…
FragLegs May 24, 2024
7ae702d
Respond to PR feedback
FragLegs May 24, 2024
9f942f0
Update RFC references
FragLegs Jun 6, 2024
78eb6bb
Make it clear that HTTPS is required for the jwks_uri and all stream …
FragLegs Jun 7, 2024
b7b8e8a
Add RFC9110 to references
FragLegs Jun 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 14 additions & 6 deletions openid-sharedsignals-framework-1_0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,6 +107,7 @@ normative:
RFC8615:
RFC8935:
RFC8936:
RFC9110:
RFC9493:
CAEP:
author:
Expand Down Expand Up @@ -563,31 +564,31 @@ jwks_uri
> OPTIONAL. URL of the Transmitter's JSON Web Key Set {{RFC7517}} document.
This contains the signing key(s) the Receiver uses to validate signatures from
the Transmitter. This value MUST be specified if the Transmitter intends to
generate signed JWTs.
generate signed JWTs. If present, this URL MUST use HTTP over TLS {{RFC9110}}.

delivery_methods_supported

> RECOMMENDED. List of supported delivery method URIs.

configuration_endpoint

> OPTIONAL. The URL of the Configuration Endpoint.
> OPTIONAL. The URL of the Configuration Endpoint. If present, this URL MUST use HTTP over TLS {{RFC9110}}.

status_endpoint

> OPTIONAL. The URL of the Status Endpoint.
> OPTIONAL. The URL of the Status Endpoint. If present, this URL MUST use HTTP over TLS {{RFC9110}}.

add_subject_endpoint

> OPTIONAL. The URL of the Add Subject Endpoint.
> OPTIONAL. The URL of the Add Subject Endpoint. If present, this URL MUST use HTTP over TLS {{RFC9110}}.

remove_subject_endpoint

> OPTIONAL. The URL of the Remove Subject Endpoint.
> OPTIONAL. The URL of the Remove Subject Endpoint. If present, this URL MUST use HTTP over TLS {{RFC9110}}.

verification_endpoint

> OPTIONAL. The URL of the Verification Endpoint.
> OPTIONAL. The URL of the Verification Endpoint. If present, this URL MUST use HTTP over TLS {{RFC9110}}.

critical_subject_members

Expand Down Expand Up @@ -762,6 +763,13 @@ which can be used by Event Receivers to create and delete one or more Event Stre
The API can also be used to query and update the Event Stream's configuration and status,
add and remove Subjects, and trigger verification for those streams.

Unless there exists some other method of establishing trust between a Transmitter and
FragLegs marked this conversation as resolved.
Show resolved Hide resolved
Receiver, all Stream Management API endpoints MUST use standard HTTP
authentication and authorization schemes, as per {{RFC9110}}.
This authorization MUST associate a Receiver with one or more stream IDs and "aud" values,
such that only authorized Receivers are able to access or modify the details of the
associated Event Streams.

~~~
+------------+ +------------+
| | Stream Config | |
Expand Down
Loading