ACME with Dynu API Secret and Client ID do not update in /etc/acme/account.conf
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
The configuration file for ACME on Openwrt in /etc/config/acme allows entries for API credentials per certificate. However, after the first time you enter these crendentials for a Dynudns API it seems they are copied into /etc/acme/account.conf and all future requests rely on /etc/acme/account.conf. If you update your credentials either in Luci or in the config file /etc/config/acme .....the updated credentials are not replaced in /etc/acme/account.conf. So two problems really:
- It appears by configuring of each certificate when multiple certificates are managed under acme should support DNS api credentials per certificate but it doesn't really work that way at least not with Dynu.
- If you update your API credentials the update is not applied to /etc/acme/account.conf. So you have to figure that out yourself and edit that file manually.
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 tracing how credentials from /etc/config/acme are written to /etc/acme/account.conf, with attention to Dynu credentials and multiple certificates. Done means updated credentials are applied without manual editing and the intended per-certificate behavior is explicit and working.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100