-
Notifications
You must be signed in to change notification settings - Fork 16
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.
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
Fix description of error code for invalid state #182
Merged
FragLegs
merged 1 commit into
main
from
171-clarify-expected-response-when-state-is-incorrect-for-verification-event
Jun 10, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1761,8 +1761,8 @@ sub_id | |
Upon receiving a Verification Event, the Event Receiver SHALL parse the SET and | ||
validate its claims. In particular, the Event Receiver SHALL confirm that the | ||
value for "state" is as expected. If the value of "state" does not match, an | ||
error response of "setData" SHOULD be returned (see Section 2.3 of | ||
{{RFC8935}} or {{RFC8936}}). | ||
error response with the "err" field set to "invalid_state" SHOULD be returned (see Section 2.4 of | ||
{{RFC8935}} or Section 2.4.4 of {{RFC8936}}). | ||
|
||
In many cases, Event Transmitters MAY disable or suspend an Event Stream that | ||
fails to successfully verify based on the acknowledgement or lack of | ||
|
@@ -2188,6 +2188,25 @@ Subject Identifiers for Security Event Tokens {{RFC9493}} specification. | |
The `ssf-configuration` well-known endpoint is registered in IANA's Well-Known URIs | ||
registry, as defined by {{RFC8615}}. | ||
|
||
IANA is asked to assign the error code "invalid_state", as defined in {{verification-event}}, to the | ||
Security Event Token Error Codes section of the Security Event Token registry, as defined | ||
in Section 7.1 of {{RFC8935}}. The following information is provided as required by the | ||
registration template: | ||
|
||
Error Code | ||
|
||
> invalid_state | ||
|
||
Description | ||
|
||
> Indicates that a Verification event contained a "state" claim that does not | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. To align with other SSF error code description, suggesting following
|
||
match the value expected by the Receiver. | ||
|
||
Change Controller | ||
|
||
> OpenID - Shared Signals Working Group | ||
|
||
|
||
--- back | ||
|
||
# Acknowledgements | ||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FragLegs I feel we should link
2.3
from RFC8935 or an example