-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John,
On 12/6/17 7:32 AM, Johan Compagner wrote:
> On 1 December 2017 at 16:44, Mark Thomas wrote:
>
>> On 01/12/17 14:57, Chris Cheshire wrote:
>>> I see in the changelog for 8.5.24
>>>
>>> 60762: Add the ability to make changes to the TLS confi
On 1 December 2017 at 16:44, Mark Thomas wrote:
> On 01/12/17 14:57, Chris Cheshire wrote:
> > I see in the changelog for 8.5.24
> >
> > 60762: Add the ability to make changes to the TLS configuration of a
> > connector at runtime without having to restart the Connector. (markt)
> >
> > Does this
On 06/12/17 01:06, George S. wrote:
>
>
> On 12/1/2017 8:44 AM, Mark Thomas wrote:
>> On 01/12/17 14:57, Chris Cheshire wrote:
>>> I see in the changelog for 8.5.24
>>>
>>> 60762: Add the ability to make changes to the TLS configuration of a
>>> connector at runtime without having to restart the
On 12/1/2017 8:44 AM, Mark Thomas wrote:
On 01/12/17 14:57, Chris Cheshire wrote:
I see in the changelog for 8.5.24
60762: Add the ability to make changes to the TLS configuration of a
connector at runtime without having to restart the Connector. (markt)
What strikes me as odd is that SSL C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 12/1/17 10:44 AM, Mark Thomas wrote:
> On 01/12/17 14:57, Chris Cheshire wrote:
>> I see in the changelog for 8.5.24
>>
>> 60762: Add the ability to make changes to the TLS configuration
>> of a connector at runtime without having to resta
On 01/12/17 14:57, Chris Cheshire wrote:
> I see in the changelog for 8.5.24
>
> 60762: Add the ability to make changes to the TLS configuration of a
> connector at runtime without having to restart the Connector. (markt)
>
> Does this mean we can now update SSL certificates without bouncing the
I see in the changelog for 8.5.24
60762: Add the ability to make changes to the TLS configuration of a
connector at runtime without having to restart the Connector. (markt)
Does this mean we can now update SSL certificates without bouncing the
connector?
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nikko,
On 3/9/2011 2:26 AM, Nikko Nikko wrote:
> Thanks for the answers! I have one IP and wildcard certificate which
> I signed using local CA. I want to have different trust stores for
> client certificate authorization. It is a small PoC/demo and
Thanks for the detailed answers.
I should find another solution.
Nikko.
2011/3/9 Ognjen Blagojevic
> Nikko,
>
>
> On 9.3.2011 8:26, Nikko Nikko wrote:
>
>> Thanks for the answers! I have one IP and wildcard certificate which I
>> signed using local CA. I want to have different trust stores f
Nikko,
On 9.3.2011 8:26, Nikko Nikko wrote:
Thanks for the answers! I have one IP and wildcard certificate which I
signed using local CA. I want to have different trust stores for client
certificate authorization. It is a small PoC/demo and I do not have 2 IP-s.
The example above is using 2
Hi,
Thanks for the answers! I have one IP and wildcard certificate which I
signed using local CA. I want to have different trust stores for client
certificate authorization. It is a small PoC/demo and I do not have 2 IP-s.
The example above is using 2 IP-s and I did not get how to create
configu
On 8.3.2011 14:51, Borut Hadžialić wrote:
Maybe if your domains are really similar to host1.myhost.com and
host2.myhost.com you could use a wildcard certificate (*.myhost.com)
or if you are using a self-signed certificate and want just https
encryption and not server verification - then you could
Hi
> If you have only 1 ip address then you might have a problem. The problem
> with name based virtual hosts under https/ssl is that ssl handshake (which
> involves server sending a certificate for some
> domain) happens after tcp/ip connection is established - before the HOST
> part of the http
On 8.3.2011 13:57, Nikko Nikko wrote:
Is It possible to define 2 SSL connectors for 2 different virtual domain
domains? For example I want to define 2 virtual hosts: “host1.myhost.com”
and “host2.myhost.com” and want to have different trust store for each of
them. I want to run them in one
gt;
>
> Is It possible to define 2 SSL connectors for 2 different virtual domain
> domains? For example I want to define 2 virtual hosts: “host1.myhost.com”
> and “host2.myhost.com” and want to have different trust store for each of
> them. I want to run them in one and the sam
Hi,
Is It possible to define 2 SSL connectors for 2 different virtual domain
domains? For example I want to define 2 virtual hosts: “host1.myhost.com”
and “host2.myhost.com” and want to have different trust store for each of
them. I want to run them in one and the same Tomcat instance
16 matches
Mail list logo
