Bug #16651
closed
acme 1.0.5 config page for editing a cert displays (and then saves) incorrect ACME Account value
0%
Description
I have two ACME accounts configured in Services / Acme Certificates / Account keys:
| Name | CA |
|---|---|
| Let's Encrypt test account key | letsencrypt-staging-2 |
| Let's Encrypt production account key | letsencrypt-production-2 |
I have certificates saved under the Certificates tab which use the "Let's Encrypt production account key". The listing on that tab shows it correctly. However when edit any of them, the edit page's ACME Account combobox shows "Let's Encrypt test account key" selected. The config.xml is correct, and everything functions correctly, so this is purely a display issue — until I go to save it. If I open one of these for editing and forget to change the account to the production key, then when I save whatever I was editing it will change the account to the test key.
I have observed this as recently as version 1.0.5 but I for sure was seeing this in some versions prior. I don't recall how far back.
Related issues
Updated by Jim Pingle 2 days ago
This appears to be related to #16650 -- the same type of cause seems to be responsible for both of them. It isn't selecting the entry because the config data doesn't match, and it doesn't match because it's encoded in the config and not decoded when read back. Though I'm hesitant to mark this as duplicate since both behaviors are different and need checked separately.
Without the ' char in the key description it works as expected, so if you want to work around this, rename your account key entries.
Updated by
Updated by Jim Pingle 2 days ago
- Status changed from New to Duplicate
- Assignee set to Jim Pingle
After working with this and finding a fix, it is the same root cause behind both, and fixing one fixes both, so no need for a second issue.
Updated by Jim Pingle 2 days ago
- Is duplicate of Bug #16650: ACME account key and certificate editing pages unnecessarily double encode configuration data added