For kubernetes we need to support IP's as subjectAltName.
Envisioned usage for this is that tagging of extras in SAN will be done on the server/tooling site.
Suggested usage
caramel_tool --add-san IP 10.10.0.1 $ID
Perhaps a --list-san and --clear-san needed too.
Implementation:
- new table with:
id | csr.id (fk not null) | option ENUM ("IP" ,"DNS") | string value (not null)
And rather than adding SAN DNS in the sign method, we add it on the request received/inserted, and populate it further.
For kubernetes we need to support IP's as subjectAltName.
Envisioned usage for this is that tagging of extras in SAN will be done on the server/tooling site.
Suggested usage
caramel_tool --add-san IP 10.10.0.1 $IDPerhaps a --list-san and --clear-san needed too.
Implementation:
id | csr.id (fk not null) | option ENUM ("IP" ,"DNS") | string value (not null)And rather than adding SAN DNS in the sign method, we add it on the request received/inserted, and populate it further.