feat: implement hmac authentication for create-* and sign-* endpoints #25
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.
This PR introduces a simple out-of-the-box HMAC authentication and authorization scheme for write operations, which are currently wide open.
It introduces a non-optional
KORMIR_HMAC_SECRET
environment variable to define an HMAC secret. Authentication can be disabled by setting theKORMIR_HMAC_SECRET
environment variable tonone
.The server expects the client to send a hex-encoded HMAC signature, generated using the same secret, in the
X-Signature
HTTP request header.