-
Notifications
You must be signed in to change notification settings - Fork 90
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
Private ACME CA doesn't send "challenges" key #824
Comments
According to RFC 8555 |
Ah okay. Is there a way to see the response of |
You could add some debug statements that write the replies to a log, for example using https://pypi.org/project/q/. |
Appreciate the assistance! As this request is directly against the RFC I'll close this. |
I implemented some code which accepts the missing |
SUMMARY
Our private ACME server doesn't require any challenges, as long as we have a valid ACME account (granted via an external account binding). The acme_certificate role appears to be looking for a "challenges" key in the response from the ACME server, but since ours doesn't provide that it fails, even when passing
challenge: "no challenge"
.ISSUE TYPE
COMPONENT NAME
community.crypto.acme_certificate
More specifically it appears to be on line 144 of challenges.py.
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
MacOS Sonoma 14.3.1
Homebrew version 4.4.11
STEPS TO REPRODUCE
Playbook calling custom role
Custom Role
EXPECTED RESULTS
Certificate to be ordered & returned to Ansible.
ACTUAL RESULTS
ansible_certificate role expects
challenges
to be a returned key, but our ACME CA doesn't return that since it's private and authenticated via an EAB.The text was updated successfully, but these errors were encountered: