-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Closed
Description
Describe the bug
The Infisical PKI ACME implementation doesn't support issuance of IP certificates.
Alt: This limitation isn't documented
To Reproduce
Steps to reproduce the behavior:
- Create Root CA in Infisical
- Create Certificate Policy (all all IP & DNS SANs)
- Create Certificate Profile (use ACME, use EAB, & skip validation)
- Copy EAB & Directory resources
- Run the following
lego -d 127.0.0.1 -s https://eu.infisical.com/api/v1/cert-manager/acme/profiles/REPLACEME/directory -a -eab --kid REPLACEME --hmac REPLACEME --http run - See Only DNS identifiers are supported
urn:ietf:params:acme:error:unsupportedIdentifier :: Only DNS identifiers are supported
Expected behavior
ACME issuer to approve a new order containing IP addresses in the SAN.
This is rather critical for internal PKI usage.
Platform you are having the issue on:
Infisical Cloud + Linux Desktop
Additional context
You'll need to install the Lego ACME client to validate issue since certbot rejects IP addresses: https://go-acme.github.io/lego/
I believe this is the issue:
| throw new AcmeBadCSRError({ message: "Invalid CSR: Only DNS subject alternative names are supported" }); |
Not sure if this is an intended mechanic really, but seemed unintuitive for internal PKI.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels