Just for info, I have now updated the default behaviour of the keystore to
always return a valid certificate (if one is available), and to use (if
available) the host name information in the client's connection to pick a
certificate which matches the expected address (work done under QPID-7567).
rgodfrey wrote
> On 27 October 2017 at 10:43, Vavricka
> vavricka.tomas@
> wrote:
>
> In the period 28.10.2017 10:00 - 30.10.2017 10:00; both certificates are
> valid... the broker can't really know which is "preferred" by the client,
> I
> would think that we should always go with the one
On 27 October 2017 at 10:43, Vavricka wrote:
> I can imagine these situations where it can be helpful.
>
> 1.
>
> * There is active/passive cluster (provides a fully redundant instance of
> each node, which is only brought online when its associated primary node
>
I can imagine these situations where it can be helpful.
1.
* There is active/passive cluster (provides a fully redundant instance of
each node, which is only brought online when its associated primary node
fails) environment where Java broker is running on node1
* Shared drive is used for
On 26 October 2017 at 13:27, Vavricka wrote:
> Hi,
>
> I have working amqps in Java broker. Clients can connect without any
> issues.
>
> You can specify certificate alias, if there are multiple certificates in
> keystore. I wonder if there is possibility to use any of