6 ms·
Humble question: Why not use Let's encrypt via DNS API? Works both internally & on public networks.
by Helmut10001 3y ago
Humble question: Why not use Let's encrypt via DNS API? Works both internally & on public networks.
- wasmitnetzen 3y agoLet's Encrypt is only 8 years old, that's not enough time for a lot of corporate IT policies to allow its usage.
- bityard 3y agoIn an "Enterprise" setting, the dev or ops team that needs certificates for internal services often has no direct access to the company's external web site or DNS, which may be owned by some other team like marketing or IT. So the options can boil down to jumping through bureaucratic hoops (if they even exist) for every request, or kludge together some other half-baked system that sorta gets the job done. Ask me how I know.
- Helmut10001 3y agoMakes sense. I mean, in case of wildcard certificates, number of requests/access could be reduced to 1x per subdomain, but still. I have the same problem at my university.