Steps toward an RFC 9241 HTTP Message Signatures implementation #109
Conversation
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
We want to use request signing to authenticate service-to-service traffic within Replicate. Request signing is an attractive option for a number of reasons. Two important ones: 1. we authenticate individual requests, not a communication channel shared between many requests (looking at you, mTLS) 2. we have access to authentication data, signature parameters, etc., at the HTTP layer, which makes enforcing per-endpoint requirements much easier This commit starts to lay the groundwork for an implementation of HTTP Message Signatures in compliance with RFC 9241. This is by no means a complete implementation of the spec, but it should already cover almost everything needed for deployment at Replicate. Notably, there is currently no support for signing responses, only requests. Currently only signing is implemented. Verification code will initially only be needed in Python, although we'll likely want to add it here so we can more effectively test this.
nickstenning
force-pushed
the
request-signing
branch
from
c8e98b2
to
af84ae0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We want to use request signing to authenticate service-to-service traffic within Replicate. Request signing is an attractive option for a number of reasons. Two important ones:
This commit starts to lay the groundwork for an implementation of HTTP Message Signatures in compliance with RFC 9241. This is by no means a complete implementation of the spec, but it should already cover almost everything needed for deployment at Replicate.
Notably, there is currently no support for signing responses, only requests.
Currently only signing is implemented. Verification code will initially only be needed in Python, although we'll likely want to add it here so we can more effectively test this.