Hi Adel,
It was not clear from your email if you got SSL working on your dispatch
router. Here are the steps I used to create the ca certs/server certs using
openssl and use them in the dispatch router -
# Create the root CA private key for the CA cert, this key is password protected
Hello -
I have been attempting to use the Proton libraries to access (send/receive
messages) the Azure Service Bus. We have had some issues getting the libs to
build correctly using the C++ bindings on both Windows and Linux. Is there a
site that maintains correctly built libs so we don't
We find the issue. It was a cached configuration file in our system.
Apologies for the inconvenience caused.
Regards,Adel
> From: adelbout...@live.com
> To: users@qpid.apache.org
> Subject: RE: [Qpid-dispatch] Duplication between sslProfile and connector
> options
> Date: Mon, 20 Jun 2016
I have debugged the python management part which gets the attribute and it
seems to be not reading them from the json config file as it is supposed to. Am
I missing something?
python/qpid_dispatch/management/entity.py (Added code to print attributed to
file)
class EntityBase(object):
"""
I found something which might be interesting. Actually the config of the
Listener is not taken into consideration.
With the config you proposed, if you check the below log in the dispatcher, the
parameters are not taken into consideration. For example, the requiresSSL is
always False although
Hello,
I took the latest available dispatcher version (0.6.0-RC4) and replayed my test
and tried to send a message using a JMS producer.
The connection is failing at the level of the handshake. I also have the SSL
debug output java side. On the dispatcher side, I can see that it is receiving
