Open rjbasitali opened 1 week ago
I guess I don't understand a few things.
Now, I have to add support for issuing on-demand wildcard certificates
What is your use case for on-demand wildcard certificates? That seems unusual to me.
I've tried calling the following function from my on-demand function if a domain is allowed to have a wildcard, but it doesn't trigger anything
That function starts managing a wildcard domain asynchronously with on-demand enabled, which means that it won't "trigger" anything until a TLS server associated with that config receives a handshake for a domain name in its SNI, but the SNI will never be a wildcard.🤷♂
What is your question?
I have a proxy server which is using certmagic to issue
on-demand
TLS certificates, theon-demand
function checks cache/database to decide if the domain is allowed or not so the TLS certificate is issued or denied, which works perfectly fine.Now, I have to add support for issuing
on-demand wildcard certificates
and I'm using the sameon-demand
function to decide if the domain name is allowed to have a wildcard certificate and get the dns provider config from the cache/database for it so I could use the appropriate implementation oflibdns
(e.g.godaddy
) to issue the wildcard using the dns challenge.What have you already tried?
I've tried calling the following function from my
on-demand
function if a domain is allowed to have a wildcard, but it doesn't trigger anything (creation of certificate or errors):In the
on-demand
function I return an errorerrors.New("managing wildcard certificate async")
so it doesn't continue issuing TLS certificate forabc.xyz.com
and instead create a wildcard certficate in the above function*.xyz.com
.Bonus: What do you use this package for, and does it help you?
I'm using it in a custom reverse proxy written in Go and it has really helped me for the past years, as this reverse proxy also needs to provision the TLS certificates.