EHS6, TLS/SSL and Paho | Telit Cinterion IoT Developer Community
February 5, 2017 - 10:06am, 1934 views
I am trying to connect an EHS6 to the AWS IoT MQTT broker.
I have certs and keys that are known to work: I can create a
jks keystore and connect with Paho as an app in Windows and
Linux. But when I follow the directions from the Gemalto
Showcase, I always get an MQTT exception (from
SSLMicroNetworkModule (line 95)). That is an exception from
the call to connector.open(uri).
I can't walk into that code (it's part of ME), and the exception
isn't very helpful in determining why the open fails. I can't
turn on JVM debugging (ie -Djavax.net.debug=all) to see the
handshakes/negotiation. I really have no idea why the connection
I'm pretty sure the issue is either the key/cert
conversion to "*.bin" files, or how I've loaded the bin
files into the EHS6 (I'm also pretty sure I've followed the
documented approach to the letter).
Any suggestions for how to debug this condition
would be greatly appreciated.
Could you please check the module's firmware version with "ATI1" ?
It is possible that you have the version that does not support connections to AWS IoT MQTT yet.
I'm using 2.0.15
I have 3.0.14 available to me.
As an aside, is there anyplace that describes
the ^SJMSEC command in more detail? I'd be
curious to know how/if it uses keystores, what
the format of those keystores are, etc (there's
very little info about this command in the AT
So you have the latest officially released versions of the firmware for revision 2 and 3.
But the newer firmware version is necessary for this to work. Please contact your local Gemalto technical sales person for more information and ask if you could get the firmware.
As for the documentation the Java User's Guide document covers this subject much more deeply than the AT commands specification.