-
Notifications
You must be signed in to change notification settings - Fork 503
Open
Labels
bugneeds triageWaiting for discussion / prioritization by teamWaiting for discussion / prioritization by team
Description
Steps to Reproduce
- Run an Ansible playbook that tries to deactivate all authz for an existing ACME v2 order. (e.g. https://docs.ansible.com/ansible/latest//collections/community/crypto/acme_certificate_deactivate_authz_module.html)
- Observe this is the Step CA logs: expected POST-as-GET
- Depending on the particular Ansible module, you'll get a warning indication the authz could not be deactivated.
Your Environment
- OS - Running in a Podman container
step-ca
Version - 0.28.1
Expected Behavior
IIUC the RFC correctly, the JWS payload should not be empty and should instead contain something like this:
{
"status": "deactivated"
}
Actual Behavior
Get the error "expected POST-as-GET" and the authz is not deactivated.
Additional Context
certificates/acme/api/middleware.go
Line 558 in b22e186
render.Error(w, r, acme.NewError(acme.ErrorMalformedType, "expected POST-as-GET")) - https://docs.ansible.com/ansible/latest//collections/community/crypto/acme_certificate_deactivate_authz_module.html
- https://github.com/ansible-collections/community.crypto/blob/a42e541326796aae2b5ff02504af925df14546e5/plugins/module_utils/acme/challenges.py#L325-L340
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
Metadata
Metadata
Assignees
Labels
bugneeds triageWaiting for discussion / prioritization by teamWaiting for discussion / prioritization by team