|
On 3 Sep 00, at 10:21, Jacob W Anderson wrote:
> Well, certificates are bound to the absolute server name. So on a server
> farm, with lots of real servers, you end up having web1.foo.com,
> web2.foo.com, and each of them has it's own certificate. You can not
> install the same certificate into each server because the CSR is different
> for each of them. It's lame, but a sad reality of non-terminated SSL.
>
> If ANYBODY out there knows how to get around this, I am ALL EARS! :) At
> ~$800 each, multiple certificates get REALLY REALLY lame, and fast. Not
> only that, but they become an administrative nightmare when you have more
> than three real servers.
The solution is simple: just don't do that :-)
Simply, get a certificate for www.whoever.com and run ALL servers
under the name www.whoever.com using the same certificate.
There is no need to give them different names like www1, www2,
etc.
Best regards,
Axel Dunkel
---
Systemberatung A. Dunkel GmbH, Gutenbergstr. 5, D-65830 Kriftel
Tel.: +49-6192-9988-0, Fax: +49-6192-9988-99, E-Mail: ad@xxxxxxxxx
|
