We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello, I am trying to use a REST subscription with signature verification based on the docs provided here: https://www.medplum.com/docs/subscriptions/subscription-extensions#signatures
I noticed that the signature doesn't match for Delete events.
It looks like the signature is generated using the resource that was deleted instead of the body that is sent ({}) based on https://github.com/medplum/medplum/blob/main/packages/server/src/workers/subscription.ts#L571
Is this intentional?
I would expect any of the following would allow the signatures to match on deleted resources:
ref: discord support thread
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello, I am trying to use a REST subscription with signature verification based on the docs provided here: https://www.medplum.com/docs/subscriptions/subscription-extensions#signatures
I noticed that the signature doesn't match for Delete events.
It looks like the signature is generated using the resource that was deleted instead of the body that is sent ({}) based on https://github.com/medplum/medplum/blob/main/packages/server/src/workers/subscription.ts#L571
Is this intentional?
I would expect any of the following would allow the signatures to match on deleted resources:
ref: discord support thread
The text was updated successfully, but these errors were encountered: