security/acme-client: no account/challenge for ACME with EAB
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.2k
- Forks
- 863
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 10
Description
Is your feature request related to a problem? Please describe.
For acme2certifier or global CA (Harica/Sectigo) EAB is using. In this case is no challenge or account necessary. All data is provided when the function is called.
Like: certbot certonly --standalone --non-interactive --key-type rsa --rsa-key-size 4096 --email ... --server https://hotacme/... --domain NAME −eab−kid ID −-eab−hmac−key EAB −−cert−name NAME
Describe the solution you'd like
Please create a internal empty EAB-Account and empty EAB-Challenge thats can choice in "add certificate" so that the system only call the URL. Alternativly you can allow to input the call "certbot..." with free text.
Describe alternatives you've considered
I see no alternative way.
Additional context
no.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the security/acme-client plugin and its existing “add certificate” flow, then compare how it invokes the certbot command shown in the issue. Done means the flow can handle EAB-provided account and challenge data without prompting, or clearly supports the requested free-text command alternative, with the resulting certificate issuance verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100