5 ms·
Assuming you have something like customer_name.myapp.com as your dashboard URL, a once-off wildcard SSL for *.myapp.com should suffice, in case you are needing
by plasma 8y ago
Assuming you have something like customer_name.myapp.com as your dashboard URL, a once-off wildcard SSL for *.myapp.com should suffice, in case you are needing to grab one for each user?
- tnolet 8y agoYes, you are correct for all the customer.checklyhq.com URLs. This everyone gets because it is part of the general wildcard SSL certificate for *.checklyhq.com. However, customers want to have https://status.example.com https://status.example.com for their status pages. This is why we need to provide custom SSL certificates using Lets Encrypt.
- ec109685 8y agoHope customers don’t have cookies scoped to *.example.com
- cyberferret 8y agoThat shouldn't be an issue. Having a wildcard cert for .checklyhq.com shouldn't preclude you from having a separate subdomain cert for blog.checklyhq.com etc. In fact, we do this for our own SaaS and never had a problem. Our AWS instance is protected by *.mydomain.com SSL cert but we have other servers running on digital ocean etc. that have their own subdomains and their own SSL certs. The tricky thing for us is to filter out the subdomains that we use (e.g. [blog,status,www]), and prevent our customers from using them as their own custom subdomains with our app otherwise our whole DNS redirection doesn't work.
- imhoguy 8y agoRich subdomain blacklist should do the trick. Or alternative is: .app.mydomain.com or .mydomainapp.com Eventually require customers to have at least 4 characters names.