-
Notifications
You must be signed in to change notification settings - Fork 30
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
Signer Delete Interface (signerCertificate) #63
Comments
Hi @gregsons , a payload in a DELETE-Request is not violating any RFC in any form. The way of deleting/ revoking certificates was changed because it was required to also sign delete requests with your uploader certificate. (Please mind: It is not only moving the hash from header to body). As I can see in the linked documentation this property only affects GET requests. Have you tried sending a delete message via this proxy? |
Hi @f11h , |
Hi @gregsons , I've created a PR to adress your issue. This PR introduces an alias for accessing the delete endpoint.
|
@f11h thank you, would it be possible to add support for /signerCertificate/delete also in dgc-lib? |
Yes, I will think about it how to integrate it the best way |
I've created an issue in dgc-lib project to introduce the feature: eu-digital-green-certificates/dgc-lib#28 |
Thank you! |
Your Question
We're currently using ESB WSO2 for forwarding requests to Gateway which doesn't give possibility to forward data in body for DELETE operation. It can be configured only for GET:
https://docs.wso2.com/display/EI650/HTTP+Transport+Properties#HTTPTransportProperties-NO_ENTITY_BODY
The text was updated successfully, but these errors were encountered: