1. Caddy version (caddy version):
v2.4.0-beta.1 h1:Ed/tIaN3p6z8M3pEiXWJL/T8JmCqV62FrSJCHKquW/I=
2. How I run Caddy:
caddy run
a. System environment:
Windows 10, 20H2
b. Command:
caddy run
c. Service/unit/compose file:
none
d. My complete Caddyfile or JSON config:
localhost {
tls internal
respond "local caddy server"
}
3. The problem I’m having:
I want to configure either the “internal” pki issuer or define a new one.
Background: i want to setup a pki issuer with a root certificate/key pair based on a Windows CA, where i can get a certificate for a “subordinate CA”. The root certificate from the Windows CA is already distributed, so i won’t have to distribute another one.
I wanted to look how the “internal” issuer is defined via looking at th localhost:2019/config endpoint, but the pki app configuration is not included.
4. Error messages and/or full log output:
the config endpoint gives me this config (for the minimal Caddyfile):
"apps": {
"http": {
"servers": {
"srv0": {
"listen": [
":443"
],
"routes": [
{
"handle": [
{
"handler": "subroute",
"routes": [
{
"handle": [
{
"body": "local caddy server",
"handler": "static_response"
}
]
}
]
}
],
"match": [
{
"host": [
"localhost"
]
}
],
"terminal": true
}
]
}
}
},
"tls": {
"automation": {
"policies": [
{
"issuers": [
{
"module": "internal"
}
],
"subjects": [
"localhost"
]
}
]
}
}
}
}
5. What I already tried:
i searched for an example for configuring the pki app, but could not find one.
i also tried to get a config via localhost:2019/config/apps/pki , but the i got the answer “null”
The internal issuer is working, i get a certificate from " [Caddy Local Authority - ECC Intermediate]" and the certificate files are in the storage in the pki/authorities/local/ directory
Is this behavior (no pki config via :2019 endpoint) wanted? Or should the config be downloadable?
P.S.: when i get this working i will write a wiki entry for this