Skip to content

Commit 938645e

Browse files
committed
Add SHOULD language about checking the issuer value
1 parent a3f26b9 commit 938645e

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

openid-sharedsignals-framework-1_0.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -927,7 +927,9 @@ In order to communicate events from a Transmitter to a Receiver, a Receiver
927927
MUST first create an Event Stream. An Event Receiver creates a stream by making
928928
an HTTP POST request to the Configuration Endpoint. On receiving a valid request
929929
the Event Transmitter responds with a "201 Created" response containing a
930-
[JSON][RFC7159] representation of the stream’s configuration in the body.
930+
[JSON][RFC7159] representation of the stream’s configuration in the body. The Receiver
931+
SHOULD check the response and confirm that the `iss` value matches the Issuer from
932+
which it received the Transmitter Configuration data.
931933

932934
If a stream already exists, and the Transmitter allows multiple streams with the
933935
same Receiver, the Event Transmitter MUST respond with a new stream ID. If the
@@ -1022,7 +1024,9 @@ Errors are signaled with HTTP status codes as follows:
10221024
An Event Receiver gets the current configuration of a stream by making an HTTP
10231025
GET request to the Configuration Endpoint. On receiving a valid request, the
10241026
Event Transmitter responds with a "200 OK" response containing a [JSON][RFC7159]
1025-
representation of the stream’s configuration in the body.
1027+
representation of the stream’s configuration in the body. The Receiver
1028+
SHOULD check the response and confirm that the `iss` value matches the Issuer from
1029+
which it received the Transmitter Configuration data.
10261030

10271031
The GET request MAY include the "stream_id" as a query parameter in order to
10281032
identify the correct Event Stream. If the "stream_id" parameter is missing,
@@ -1219,7 +1223,8 @@ HTTP PATCH request to the Configuration Endpoint. The PATCH body contains a
12191223
[JSON][RFC7159] representation of the stream configuration properties to change. On
12201224
receiving a valid request, the Event Transmitter responds with a "200 OK"
12211225
response containing a [JSON][RFC7159] representation of the entire updated stream
1222-
configuration in the body.
1226+
configuration in the body. The Receiver SHOULD check the response and confirm that the
1227+
`iss` value matches the Issuer from which it received the Transmitter Configuration data.
12231228

12241229
The stream_id property MUST be present in the request. Other properties
12251230
MAY be present in the request. Any Receiver-Supplied property present in the
@@ -1307,6 +1312,8 @@ HTTP PUT request to the Configuration Endpoint. The PUT body contains a JSON
13071312
{{RFC7159}} representation of the new configuration. On receiving a valid
13081313
request, the Event Transmitter responds with a "200 OK" response containing a
13091314
JSON {{RFC7159}} representation of the updated stream configuration in the body.
1315+
The Receiver SHOULD check the response and confirm that the `iss` value matches the
1316+
Issuer from which it received the Transmitter Configuration data.
13101317

13111318
The stream_id and the full set of Receiver-Supplied properties MUST be present
13121319
in the PUT body, not only those specifically intended to be changed.

0 commit comments

Comments
 (0)