Hi,
Do you know when ldap connection with ssl will be supported?
Thanks in advance,
Raul
Hi,
I need to configure activemq-client not to perform broker cerificate
validation. I need this for testing purposes, because I need to test the
system over SSL, but I do not yet have certificate distribution solved.
In Artemis, with artemis-jms-client, there is verifyHost=false and
I am looking at options for handling local failover and disaster recovery.
Our existing primary and secondary data centre hosted services run mainly
active-passive and have SAN storage but do not support SAN replication.
There is a dedicated network between the two DC's so we have fast, reliable
The actual LDAP connection is provided by com.sun.jndi.ldap.LdapCtxFactory
which I believe already supports SSL. I think you just need to set
"connectionProtocol" config parameter to "ssl".
Justin
On Wed, Nov 29, 2017 at 3:18 AM, Raul Valdoleiros <
raul.valdoleiros.olive...@gmail.com> wrote:
There's nothing built in to Artemis at this point specifically for the DR
use case. However, I believe the "data" directory (where persistent data
is stored by default) can be replicated (e.g. via a block-level storage
replication solution) or "shipped" via an external process (e.g. rsync) to
a
Hi,
I'm trying to connect 2 instances of Avtivemq 5.14.0 together using a JMS
bridge. I am also using the JaasCertificateAuthenticationPlugin.
One broker has no JMS bridge configuration but is using the
JaasCertificateAuthenticationPlugin and is using an SSLContext.
The second broker is using a
Thanks Justin. Do you know what sort of considerations I would need to make
if doing shipping, e.g.
1) What config, if any, would the node in the secondary DC need to have in
common with the nodes in the primary DC? e.g. see the warning box regarding
copying data directories and unique node id
> What config, if any, would the node in the secondary DC need to have in
common with the nodes in the primary DC?
It would need to have the same essential configuration (e.g. same
addresses, queues, etc.), but it wouldn't necessarily need to be clustered
or have its own HA config, etc.
> I
In 5.x it isn't quite as simple.
To trust all you'll need to extend ActiveMQSslConnectionFactory and
override the createTrustManager() method. This should work:
@Override
protected TrustManager[] createTrustManager() throws Exception {
return new TrustManager[] { new X509TrustManager() {
public
After reading the discussion and thinking about it I think I am on board
with going with ActiveMQ 6.
What's the next step with this? Do we want to propose a vote or keep the
discussion open longer?
On Thu, Nov 23, 2017 at 3:09 PM, Gary Tully wrote:
> I think ActiveMQ
This discussion has been open for 15 days. IMO we should move ahead with
whatever is the next step. Vote probably?
On Wed, Nov 29, 2017 at 2:10 PM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> After reading the discussion and thinking about it I think I am on board
> with
11 matches
Mail list logo