mirror of
https://github.com/shred/acme4j.git
synced 2025-12-16 11:24:01 +08:00
The ssl.com staging server's certificate seems to be unmonitored, causing the acme4j build chain to break from time to time when their certificate has expired. As this is blocking development, I have decided to disable all related unit tests, and add a corresponding note to the documentation. The acme4j ssl.com provider is marked as experimental now, since it is not fully covered by unit tests anymore.
1.5 KiB
1.5 KiB
SSL.com
Web site: SSL.com
Available since acme4j 3.2.0. This provider is experimental!
Connection URIs
acme://ssl.com,acme://ssl.com/ecc- Production server, ECDSA certificate modeacme://ssl.com/rsa- Production server, RSA certificate modeacme://ssl.com/staging,acme://ssl.com/staging/ecc- Testing server, ECDSA certificate modeacme://ssl.com/staging/rsa- Testing server, RSA certificate mode
Note
- This CA requires External Account Binding (EAB) for account creation. However, the CA's directory resource returns
externalAccountRequiredasfalse, which is incorrect. If you use one of theacme:URIs above, acme4j will patch the metadata transparently. If you directly connect to SSL.com viahttps:URI though,Metadata.isExternalAccountRequired()could return a wrong value. (As of February 2024) - The certificate of the ssl.com staging server seems to be unmonitored. When it expires, an
AcmeNetworkExceptionis thrown which is caused by aCertificateExpiredException. There is nothing you can do to fix this error, except to ask the ssl.com support to renew the expired certificate on their server. Please do not open an issue at acme4j. (As of June 2024)
Disclaimer
acme4j is not officially supported or endorsed by SSL.com. If you have acme4j related issues, please do not ask them for support, but open an issue here.