feat(OCM): Implement ISignedCloudFederationProvider for deck - #8261
Conversation
When an app recieves OCM notifications, core needs to be able to resolve the remote seerver that sent the notification so that it can verify the signature of the notification. This patch implements the ISignedCloudFederationProvider interface for the deck app, so that this can happen. Signed-off-by: Micke Nordin <kano@sunet.se>
a6ac408 to
f83d8ec
Compare
|
馃悽 Performance warning. |
|
馃悽 Performance warning. |
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
Summary
When an app recieves OCM notifications, core needs to be able to resolve the remote server that sent the notification so that it can verify the signature of the notification.
This patch implements the ISignedCloudFederationProvider interface for the deck app, so that this can happen.
Checklist
I did not include any extra test, since the current test suite caught this error.
See docs(OCM): ISignedCloudFederationProvider needed for OCM notification聽documentation#15444