TLS 1.1 removal and disabling of weak cipher suites
At the moment, Bosch IoT Insights still supports the TLS version 1.1.
Our goal is to always offer an up-to-date and secure service for the device communication. However, the TLS version 1.1 has been considered insecure. (IETF)
If your devices or applications still use the TLS version 1.1, they will no longer be able to connect to Bosch IoT Insights after october 2021.
As a customer having a paid plan §15.3 Changes of the Service and the Terms and Conditions of the SaaS Terms and Conditions applies : “[…] If Customer does not object within 30 days of receipt of the notification and continues to use the Service after expiry of the period for objection, then the changes shall be deemed to have been effectively agreed as from the expiry date of the time limit. In the event of an objection, the contractual relationship shall be continued subject to the conditions applying hitherto. If an objection is raised, Provider is entitled to terminate the contractual relationship subject to a one (1) month’ notice period.”
Our API will only support the following cipher suites and therefore only TLS1.2 or higher:
|TLS Version||Cipher Suite Name (IANA/RFC)||Hex||KeyExch.||Auth.||Encryption||Bits||Cipher Suite Name (OpenSSL)|
For testing purposes, we offer an endpoint with the future TLS policy. Please note, that this is only a temporary testing environment.
As soon as we apply the TLS policy to the standard endpoints, the testing environment will be shut down.
You should therefore not connect any productive devices to these test endpoints. If you have any problems when testing, please let us know.
The test endpoint with the future TLS version and ciphers is as follows:
Depending from the response you can see if a TLS1.2 connection does work or not with your client.
For your help have a look into following table:
|Successfully responses||Failing responses|
|HTTP status 200 (optional with HTML page)||curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure|
|HTTP status 405 (optional with HTML page)|
If you have any further questions, do not hesitate to contact us.