3 ms·
You can solve this problem by using a "wildcard certificate". It's like 300$ more expensive than a normal one. You can test how it works creating your own: ht
by professorTuring 14y ago
You can solve this problem by using a "wildcard certificate". It's like 300$ more expensive than a normal one.
You can test how it works creating your own:
http://www.justinsamuel.com/2006/03/11/howto-create-a-self-signed-wildcard-ssl-certificate/ http://www.justinsamuel.com/2006/03/11/howto-create-a-self-s...
- mootothemax 14y agoYou can solve this problem by using a "wildcard certificate". It's like 300$ more expensive than a normal one. Incorrect. You cannot create a wildcard domain for every domain in existence. That would somewhat undermine the whole point of SSL. Edit: I think I misunderstood slightly. You're correct if you mean using the same domain for clients (e.g. client1.domain.com, anotherclient.domain.com), but not if you want clients to be able to use their own domains with your service. On a related note, StartSSL (http://www.startssl.com http://www.startssl.com) are a cheap option for wildcard certificates, and SSL certificates in general, since they only charge to validate your identity - you can issue as many certificates as you want (for domains you own) thereafter.
- professorTuring 14y agoI misunderstood your original concern :S, I meant what you said in your edit. I don't think there is a nice solution for the other problem =)
- Carolinaeliz 14y agohttp://www.instantssl.com/wildcard-ssl.html http://www.instantssl.com/wildcard-ssl.html Presently we are using this and good to use it!