Here is my scenario:
I will be proving hosting to various clients. I will be provisioning their servers with a default domain:
When clients create websites on their server it will auto generate sub domains:
My thought is to setup a wildcard ssl for each server domain on server creation:
That way as clients create websites on them no matter how many they create they will have a working SSL.
However, clients will have SSH access to their servers. So they could issue new certificates and validate the challenge on their server domain: Ex srv-1.mydomain.com
So here are my questions:
- What security risks or rate limit risks can you see with this?
- Can a client with access to srv-1 cause issues with a client on srv-2?
- Since my main website is mydomain.com could they also cause issue with me and my website?
- Is there a way to restrict the additions or certs created for specific domains? I only want to allow 1 ssl to be added to *.srv-1.mydomain.com and not allow any others to be created. (I will allow the clients to add their custom domains to the servers and all them to add ssl's to their custom domains.)
- I am concerned that one of my clients could go crazy and create tons of certs on their domain srv-1.mydomain.com and that would hit the rate limit for myself and other clients which would prevent me from adding new servers for new clients and providing them with an SSL. Is my concern correct?
- Is there a better way to do this?