You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: openid-sharedsignals-framework-1_0.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1712,9 +1712,12 @@ configured correctly upon successful receipt of the event. The acknowledgment of
1712
1712
a Verification Event also confirms to the Event Transmitter that end-to-end
1713
1713
delivery is working, including signature verification and encryption.
1714
1714
1715
-
An Event Transmitter MAY send a Verification Event at any time, even if one was
1715
+
A Transmitter MAY send a Verification Event at any time, even if one was
1716
1716
not requested by the Event Receiver.
1717
1717
1718
+
A Transmitter MUST respond to verification event requests even if the event is not present in the `events_requested` and / or `events_supported` fields in the Stream Configuration ({{stream-config}}).
1719
+
1720
+
1718
1721
#### Verification Event {#verification-event}
1719
1722
The Verification Event is a standard SET with the following attributes:
1720
1723
@@ -1845,7 +1848,9 @@ If the Transmitter changes the status of the stream from either
1845
1848
"paused"or "disabled" to "enabled", then it MUST send this event to any
1846
1849
Receiver that has previously been enabled to receive events for the stream.
1847
1850
1848
-
The "stream-updated" event MAY contain the following claims:
1851
+
A Transmitter MAY send a Stream Updated event even if the event is not present in the `events_requested` and / or `events_supported` fields in the Stream Configuration ({{stream-config}}).
1852
+
1853
+
The "stream-updated" event contains the following claims:
0 commit comments