I’m controlling all of ravendb.net, so that is not an issue.
Here is the full story. I’m build a database that want to use HTTPS, but it is usually deployed inside local networks, without being able to expose them externally.
In order to save the trouble of the admin the trouble of managing certificates manually, we take that on ourselves.
The end user will start the challenge process, and then call to us with a request to reserve a particular subdomain on our end.
The is effectively the username for that particular user and is reserved just for them. Then they can place nodes (a.ayende, b.ayende, etc) under that.
The local server at the customer site then call to our website with the LE DNS details and let the local server know that.
The local server then complete the LE challenge and get the certificate.
The idea is that the certificate itself never hit our servers and is completely within the customer’s own network.
That means, of course, that each local server is going to be using its own key.
We could change things so the central server will handle the entire process and hand the certificate back to the user from the central location, but I would rather avoid it unless this is required.