NeySlim/ultimate-ca-manager v2.182-rc2

on GitHub

[2.181] - 2026-06-30

Added

• Multi-CA management for the ACME client — UCM can now issue certificates from several external ACME authorities (Let's Encrypt, Actalis, ZeroSSL, Google Trust Services, HARICA…) instead of a single one. ACME CA accounts are managed from the UI (CRUD, per-account External Account Binding, default selection, registration status), each certificate request picks its issuing CA, and the order is pinned to that account so renewals stay on the same authority. The AcmeClientOrder.acme_client_account_id foreign key (migration 047) links each order to its external CA account; AcmeClientService.for_issuance(environment, account_id=) resolves explicit account > configured custom directory > Let's Encrypt environment, and for_order(order) reuses the pinned account on verify/finalize/status/renewal (#149).

[2.180] - 2026-06-30

Fixed

• Custom ACME CA directory and EAB are now honored for issuance and renewal — when a custom ACME directory URL was configured in Settings → ACME client (e.g. Actalis, ZeroSSL, Google Trust Services) together with External Account Binding credentials, certificate issuance and renewal still went to Let's Encrypt instead of the configured CA. The custom directory and the EAB persisted in SystemConfig were never used by the issuance/renewal path; acme.client.directory_url was effectively dead for issuance. A new AcmeClientService.for_issuance() factory reads the configured custom directory (over the Let's Encrypt staging/production mapping) and backfills legacy EAB from SystemConfig onto the AcmeClientAccount row, and for_order() resolves the issuing account from the order's recorded account_url so an order keeps its CA across changes to the directory setting. All issuance, verify, finalize, status, auto-poll and renewal entry points now route through these factories (#147).

Full history: CHANGELOG.md