Peter Crowther wrote:
>
>> Or is the IP address tied to the (wildcard) certificate?
>
> IP addresses are never tied to certificates. Certificates allow browsers
> to authenticate based on the common name in the certificate, and the
> hostname that the browser is using to access the site.
>
Y
Darren Kukulka wrote:
>
> Why not opt for a wildcard certificate for the domain, if that's
> applicable (e.g. *.yourcompany.com)
>
Hi Darren,
Interesting idea! What are the restrictions on wildcard certificates? If I
have two subdomains with one wildcard certificate, do I still need the two
IP
awarnier wrote:
>
> i_am_superman wrote:
>>
>>
>> It's gonna be a public government website, so a self-signed certificate
>> will
>> not be an option :-)
> Considering the amount of taxpayer money that governments are currently
> pumping in
Gregor Schneider wrote:
>
> How about a self-seigned cert?
>
> A nasty browser-window will pop up once, however, the users could
> import the server-cert into their browser, and then they#re done
>
It's gonna be a public government website, so a self-signed certificate will
not be an option :
Peter Crowther wrote:
>
>> From: i_am_superman [mailto:ee...@objectivation.nl]
>> is there a simple way to map one
>> domain name to two different SSL connectors?
>
> I don't think there is, unless you want part of your application to be
> accessible from
Hi y'all,
I have a fairly complex issue regarding Tomcat server configuration, so I'll
try to explain:
I have two web applications that need to run in one Tomcat server.
Application 1 needs client certificates, so I need to configure an SSL
connector with 'clientAuth="yes"'
Application 2 needs
