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

Clarify need (or not) for authentication on Regsiter Signed Statement #26

Merged
merged 2 commits into from
Aug 20, 2024
Merged

Clarify need (or not) for authentication on Regsiter Signed Statement #26

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
90e9a0a
Clarify need (or not) for authentication on Regsiter Signed Statement
Aug 9, 2024
4c98cf3
Update draft-ietf-scitt-scrapi.md
SteveLasker Aug 20, 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
7 changes: 4 additions & 3 deletions draft-ietf-scitt-scrapi.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -196,9 +196,10 @@ jwk-thumbprint:sha-256:4Fzx5HO1W0ob9CZNc3RJx28Ixpgy9JAFM8jyXKW0ClE",
Additional fields may be present.
Fields that are not understood MUST be ignored.

### Signed Statement Registration
### Register Signed Statement

Authentication MUST be implemented for this endpoint.
Authentication MAY be implemented for this endpoint.
See notes on detached payloads below.

The following is a non-normative example of a HTTP request to register a Signed Statement:

Expand All @@ -222,7 +223,7 @@ Payload (in CBOR diagnostic notation)
The Registration Policy for the Transparency Service MUST be applied to the payload bytes, before any additional processing is performed.

If the `payload` is detached, the Transparency Service depends on the authentication context of the client in the Registration Policy.
If the `payload` is attached, the Transparency Service depends on both the authentication context of the client, and the verification of the Signed Statement in the Registration Policy.
If the `payload` is attached, the Transparency Service depends on both the authentication context of the client (if present), and the verification of the Signed Statement in the Registration Policy.
The details of Registration Policy are out of scope for this document.

If registration succeeds the following identifier MAY be used to refer to the Signed Statement that was accepted:
Expand Down
Loading