sorry for butting in but...
if your customer server has the same URL name (ie.
support.btinternet.com) then it doesn't matter if you have many machines
running behind this name, you could simply copy the same certificate to
all the servers hence buying only one certificate.
but I'd guess from what you're saying that these different do _not_ have
the same URL name. Am I right?
-----Original Message-----
From: Sam Newman [mailto:[EMAIL PROTECTED]]
Sent: 13. mars 2001 09:01
To: [EMAIL PROTECTED]
Subject: Re: Encrypting password
> if the app is accessed through a single URL and loadbalanced /
proxied,
you
> still only need the one SSL cert: it's the URL, not the IP address,
that
> counts.
The situation we are in is where users connect to a server, which is our
customers servers. Each customer server would still have to have a
certificate, which is where the current sticking point is.
sam
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
