Compatible with
account required
HARICA
HARICA is implemented over ACME with EAB. The connector creates an account, orders DV/OV/EV when permitted, handles DNS-01, downloads, renews and revokes. Product catalog entries for client, email and code-signing appear only as available when the remote directory advertises them.
Verification: test_verified. Connection: unknown. Credentials: none. Live E2E: no.
HARICA ACME EAB credentials are not configured.
What sslcertificates.io can do
HARICA is implemented over ACME with EAB. The connector creates an account, orders DV/OV/EV when permitted, handles DNS-01, downloads, renews and revokes. Product catalog entries for client, email and code-signing appear only as available when the remote directory advertises them. Capabilities: acme, dv, ov, ev, client, email, code_signing. Authentication uses acme_eab.
Required permissions
HARICA ACME EAB from the subscriber portal. OV/EV need organization evidence in the HARICA account.
Setup
Open Dashboard → Integrations → HARICA. Enter the credentials described on this page. Values are encrypted at rest and never shown again. Run Test connection. Discovery runs only after authentication succeeds. Select a discovered resource. Do not paste opaque IDs unless the provider cannot enumerate them. Perform the certificate or notification action, then confirm the external system matches. Disconnect removes stored credentials and owned test resources created by sslcertificates.io.
Known limitations
Code-signing and email products are catalogued but issued only when the HARICA account includes those profiles.
Official sources
Fact checked 2026-09-20. https://repo.harica.gr/ https://www.harica.gr/en/Products/ACME HARICA is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.
Capabilities
Connect
HARICA is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.