Project

General

Profile

Actions

Bug #15733

closed

Changing the account key name does not update respective certificates

Added by Guy van der Werf 2 months ago. Updated 19 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
ACME
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
24.11
Affected Version:
2.7.2
Affected Plus Version:
Affected Architecture:

Description

Package:
acme 0.8_1

Problem:
Renaming an account key name (as seen in the tab "Account keys"), does not correctly update existing certificate metadata using that account key.

Reproduce:
  1. In the "Account key" tab, edit an account key that is used by an existing certificate.
  2. Change the account key name (field: "Name") from "Test" to "LetsEncryptTest"
  3. Return to the "Certificates" tab. Notice the "Account" column of certificates that did refer to Account Key "X", do not refer to "Y", but still refer to "X". CORRUPTION 1
  4. Repeat the above for a second account key: e.g. Name changes from "Production" to "LetsEncryptProd".
  5. In the "Certificates" tab, edit a certificate that contains a corrupted Account Key e.g. "Production" (where it should refer to "LetsEncryptProd")
  6. Notice the "Acme account" drop-down now shows an existing but incorrect Account key, "LetsEncryptTest". This is neither the correct Account key, nor is it the same as displayed in the "Certificates" tab. CORRUPTION 2

Expected:
Existing certificates should refer to the same account key by its new name.

Workaround:
Edit each certificate using the affected account key, and correct the account key in the "Acme account" drop-down.

Actions

Also available in: Atom PDF