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 1 commit
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
10 changes: 10 additions & 0 deletions openid-sharedsignals-framework-1_0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,9 +96,11 @@ normative:
title: OpenID Connect Core 1.0 - ID Token
OASIS.saml-core-2.0-os:
RFC2119:
RFC2818:
RFC6749:
RFC6750:
RFC7159:
RFC7235:
RFC7517:
RFC7519:
RFC8174:
Expand Down Expand Up @@ -762,6 +764,14 @@ 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 HTTP over TLS {{RFC2818}}
and standard HTTP authentication and authorization schemes, as per {{RFC7235}}.
The authorization MUST scope a Receiver to specific stream IDs, such that only that
FragLegs marked this conversation as resolved.
Show resolved Hide resolved
Receiver is able to access or modify the details of the Event Stream.
The Transmitter MAY describe the available authorization schemes in the Transmitter
Configuration metadata, as described in {{discovery-meta}}.

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