-
Notifications
You must be signed in to change notification settings - Fork 59
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
Allow message to be verified #48
Labels
Comments
I've created a conceptual diagram for the http signatures flow: diagram |
ewilde
added a commit
to ewilde/nats-queue-worker
that referenced
this issue
Feb 24, 2019
Resolves openfaas#48 Signed-off-by: Edward Wilde <[email protected]>
ewilde
added a commit
to ewilde/nats-queue-worker
that referenced
this issue
Feb 24, 2019
Resolves openfaas#48 Signed-off-by: Edward Wilde <[email protected]>
ewilde
added a commit
to ewilde/nats-queue-worker
that referenced
this issue
Feb 24, 2019
Resolves openfaas#48 Signed-off-by: Edward Wilde <[email protected]>
ewilde
added a commit
to ewilde/nats-queue-worker
that referenced
this issue
Feb 24, 2019
Resolves openfaas#48 Signed-off-by: Edward Wilde <[email protected]>
Derek assign: ewilde |
ewilde
added a commit
to ewilde/nats-queue-worker
that referenced
this issue
Mar 15, 2019
Resolves openfaas#48 Signed-off-by: Edward Wilde <[email protected]>
ewilde
added a commit
to ewilde/nats-queue-worker
that referenced
this issue
Mar 15, 2019
Resolves openfaas#48 Signed-off-by: Edward Wilde <[email protected]>
ewilde
added a commit
to ewilde/nats-queue-worker
that referenced
this issue
Mar 17, 2019
Resolves openfaas#48 Signed-off-by: Edward Wilde <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature: Non-repudiation for queue-worker callbacks
Suggested by: Ed Wilde @ewilde
We can use HMAC or RSA and HMAC together to sign messages when we use the X-Callback-Url. This means that receivers of the callback messages can verify the sender as the queue worker vs. some bad actor that discovered the URL.
The text was updated successfully, but these errors were encountered: