You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
I'm working on a mbedtls-based C device firmware (using MQTT protocol). Since our devices uses GPRS/3G connectivity, we need to add SSL/TLS session ticketing support to restore TLS session and avoid lots of data in case of network connection failures.
I'm testing the SSL Session Ticketing with IOTHUB servers without success. I'm using both my mbedtls-based device and openssl with my PC. In both cases Azure servers seems to ignore the SSL session resume feature.
The openssl commands i used to test it are: openssl s_client -connect myIothubInstance:8883 -reconnect
I do not think you are doing anything wrong, we currently do not support this, so it is a limitation for the SDKs.
We will consider this for the future, once we have more information on when this would be taken we'll update the thread.
@simonemarra - this is on our radar, but it's not going to be in the next few months.
I was going to suggest you create an item on user voice because this will require both service & SDK support, but it looks like you've already done so.
Since the user voice is better place to track given SDK/service nature of this, I'm going to close out this issue on GitHub. Sorry we don't have a better answer for you at present.
Hi!
I'm working on a mbedtls-based C device firmware (using MQTT protocol). Since our devices uses GPRS/3G connectivity, we need to add SSL/TLS session ticketing support to restore TLS session and avoid lots of data in case of network connection failures.
I'm testing the SSL Session Ticketing with IOTHUB servers without success. I'm using both my mbedtls-based device and openssl with my PC. In both cases Azure servers seems to ignore the SSL session resume feature.
The openssl commands i used to test it are:
openssl s_client -connect myIothubInstance:8883 -reconnect
or
openssl s_client -connect myIothubInstance:8883 -sess_out ./azure_sess_ticket
openssl s_client -connect myIothubInstance:8883 -sess_in ./azure_sess_ticket
Using my own nodejs mqtt server I have no problems at all.
The text was updated successfully, but these errors were encountered: