Knew we had to be missing something, thanks
OpenDXL
Security Intelligence Sharing
Posts by Zenbu
-
-
Tested our client with normal broker connection settings (MQTT) and had no issues. When deployed to an environment where we needed to use websockets and a proxy instead, we can't connect to the broker.
We've narrowed it down to the proxy config settings (websockets connection to broker works in env that doesn't have/need proxy)... but its not obvious whats wrong.
Here's an example of our config file:
Display MoreCode: dxlclient.config- [General]
- UseWebSockets=true
- [Certs]
- BrokerCertChain=c:\certs\testbrokercerts.crt
- CertFile=c:\certs\testclient.crt
- PrivateKey=c:\certs\testclient.key
- [Brokers]
- {11111111-1111-1111-1111-111111111111}={11111111-1111-1111-1111-111111111111};8883;testbroker.proxylab;1.1.1.11
- {22222222-2222-2222-2222-222222222222}={22222222-2222-2222-2222-222222222222};8883;testbroker2.proxylab;1.1.1.12
- [BrokersWebSockets]
- {11111111-1111-1111-1111-111111111111}={11111111-1111-1111-1111-111111111111};443;testbroker.proxylab;1.1.1.11
- {22222222-2222-2222-2222-222222222222}={22222222-2222-2222-2222-222222222222};443;testbroker2.proxylab;1.1.1.12
- [Proxy]
- Address=http://test.proxy.proxylab
- Port=9999
- User=prUser
- Password=prPass
Is there something obvious we are missing or...?
-
I want to use my own CA/certs for our Open Broker.
Before I replace the files in /dxlbroker-volume/keystore, I want to make sure I understand how they're being used.
Does anyone know what the following files are used for?
- broker.crt + broker.key
- ca-broker.crt + ca-broker.key
- ca-client.crt + ca-client.key
-
nice, didn't know this kind of information was available over messages