SSL connection with RabbitMQ about cocoamqtt HOT 9 CLOSED

If this can help, you can test the ssl connection using the test endpoint provided by Mosquitto:

mqttClient = CocoaMQTT(clientId: "clientid", host: "test.mosquitto.org", port: 8883)
mqttClient?.secureMQTT = true
mqttClient?.username = "user"
mqttClient?.password = "password"
mqttClient?.keepAlive = 90
mqttClient?.delegate = self
mqttClient?.connect()

You'll need to add this cert to your keychain.

It's also worth noting that RabbitMQ enforces the use of TLSv1.2. I had to change the dictionary provided to the startTLS function to include these two options, sadly to no avail:

GCDAsyncSocketSSLProtocolVersionMin: 8, 
GCDAsyncSocketSSLProtocolVersionMax: 8

from cocoamqtt.

After some further digging, looks like that the SSL connection is correctly established, our backend closes the connection with this error:

MQTT protocol error connect_expected for connection 

Without SSL the connection works flawlessly.

from cocoamqtt.

Ok, figured it out. It's a timing issue.
I was subscribing in a completion block triggered by the didConnect delegate. This is fine when done in plain MQTT, but not when using SSL, as you can see here:
https://github.com/emqtt/CocoaMQTT/blob/master/Source/CocoaMQTT.swift#L303
the delegate is called right away, but it should be called once the secure channel is created, in the socketDidSecure delegate method.

from cocoamqtt.

@andreamazz thanks

from cocoamqtt.

Thanks for merging.
Are you planning a new release any time soon? I would greatly appreciate that (I'm using this as a dependency for another podspec, so I need to reference a version).

from cocoamqtt.

@andreamazz Yes, tomorrow or the day after tomorrow

from cocoamqtt.

Thanks.

from cocoamqtt.

@andreamazz , v1.0.7 released.

from cocoamqtt.

Great, thank you 👍

from cocoamqtt.