Skip to content
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

[Bug]: Can't Deactivate an Authorization #2177

Open
paulcalabro opened this issue Feb 18, 2025 · 0 comments
Open

[Bug]: Can't Deactivate an Authorization #2177

paulcalabro opened this issue Feb 18, 2025 · 0 comments
Assignees
Labels
bug needs triage Waiting for discussion / prioritization by team

Comments

@paulcalabro
Copy link

paulcalabro commented Feb 18, 2025

Steps to Reproduce

  1. 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)
  2. Observe this is the Step CA logs: expected POST-as-GET
  3. 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

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).

@paulcalabro paulcalabro added bug needs triage Waiting for discussion / prioritization by team labels Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs triage Waiting for discussion / prioritization by team
Projects
None yet
Development

No branches or pull requests

2 participants