smartacme/readme.plan.md

Plan: Add wildcard domain support to SmartAcme

Goal

• Enable SmartAcme to accept wildcard domain inputs like *.domain.com or *.sub.example.com and correctly request and match wildcard certificates.

Steps

1. Extend SmartacmeCertMatcher:
   • Update getCertificateDomainNameByDomainName() to handle wildcard prefixes:
     • If input starts with *. strip the prefix and return the base domain.
     • For example:
       • *.example.com → example.com
       • *.sub.example.com → sub.example.com
       • *.a.b.example.com → a.b.example.com
   • Ensure existing logic for non-wildcards remains unchanged.
2. Update SmartAcme.getCertificateForDomain():
   • Detect wildcard inputs (domainArg.startsWith('*.')).
   • For wildcard cases, enforce DNS-01 challenge only (throw error if handlers don't support DNS-01).
   • Use the matcher result to request wildcard certificate identifiers (e.g., value: '*.baseDomain').
3. Update tests:
   • Add unit tests in test/test.certmatcher.ts for wildcard handling:
     • *.example.com → example.com
     • *.sub.example.com → sub.example.com
     • *.a.b.example.com → a.b.example.com
   • Add integration stub in test/test.smartacme.ts for wildcard input in integration mode:
     • Call getCertificateForDomain('*.domain.com') and expect returned cert domainName equals *.domain.com.
4. Update documentation (README.md) if needed.
5. Run CI (pnpm build & pnpm test) and fix any regressions.