Input Global credentials for the ACME extension

[Mattia_98]

Server operating system version

Debian 12

Plesk version and microupdate number

18.0.76

The Plesk ACME extension has finally been released and I've tried it. It works very well, props to the team.
But as it currently exists it would be difficult to include in our workflow because every time you want to issue a certificate you have to input the credentials. We issue many certificates.

It would be awesome if you could add the ability to set the ACME credentials globally for all subscriptions so that you don't have to input credentials every time you want to issue a certificate. This could be done via the panel.ini so that only server admins can do this. Something like this (example):

[ext-acme]
use-global-credentials = true ; If this is true, use credentials below
do-not-ask-credentials = true ; If this is true, do not ask credentials in the UI (either hide or gray out) use only global
acme-directory-url = https://dir.tld/dir
eab-key-id = 123456789
eab-hmac-key = 123456789

Maybe this could be paired with a toggle in the certificate issuance menu "Use global credentials".
Please think about it.

Regards,
Mattia

 

[Sebahat.hadzhi]

Hi, Mattia. Thank you for your positive feedback. I forwarded it to our team.
While this is not planned for the moment, our team is working on introducing CLI for the ACME SSL extension. When released you could optimize the process with a script containing the the necessary credentials and run it for the required domains. That's expected to arrive in Plesk Obsidian 18.0.78. We would love to hear your feedback on whether it is insufficient for optimizing the workflow.

 

[Mattia_98]

Thank you for the Information. CLI support would definitely help, Plesk API support would also be appreciated.
Is there going to be documentation for the ACME extension on https://docs.plesk.com/en-US/obsidian/administrator-guide/ soon? Like the one for LE Managing Let’s Encrypt Settings

 

[Sebahat.hadzhi]

Thank you for the question. Yes, our team is already preparing the documentation. The target date is beginning/mid May.