AHilberink Active Member Licensed User Longtime User Oct 29, 2019 #1 Hi, I have an Android4.0.2 Samsung TAB4 and want to communicate with a server over HTTPS TLS1.2 Is there a way to force OKHttp for using TLS1.2? Will it work on Android4.0? I am able to use .InitializeAcceptAll, but I prefer maximum security. Best regards, André
Hi, I have an Android4.0.2 Samsung TAB4 and want to communicate with a server over HTTPS TLS1.2 Is there a way to force OKHttp for using TLS1.2? Will it work on Android4.0? I am able to use .InitializeAcceptAll, but I prefer maximum security. Best regards, André
Erel B4X founder Staff member Licensed User Longtime User Oct 29, 2019 #2 InitializeAcceptAll will not help if your device doesn't support the server chosen algorithm. You can update the supported security provider as explained here: https://www.b4x.com/android/forum/threads/ssl-websocket-client.88472/page-2#post-560044 It will be simpler to use an Android 5+ device. Upvote 0
InitializeAcceptAll will not help if your device doesn't support the server chosen algorithm. You can update the supported security provider as explained here: https://www.b4x.com/android/forum/threads/ssl-websocket-client.88472/page-2#post-560044 It will be simpler to use an Android 5+ device.
AHilberink Active Member Licensed User Longtime User Oct 29, 2019 #3 Erel said: InitializeAcceptAll will not help if your device doesn't support the server chosen algorithm. You can update the supported security provider as explained here: https://www.b4x.com/android/forum/threads/ssl-websocket-client.88472/page-2#post-560044 It will be simpler to use an Android 5+ device. Click to expand... Thanks. After using .InitializeAcceptAll, the httpjob works fine. According to your explanation the device does support the chosen algorithm. Should I look for an incorrect installation of the certificate? My device with android 8 and 9 are working fine with standaard library of OKHttp. I will try using the update of the security provider. Best regards, André Upvote 0
Erel said: InitializeAcceptAll will not help if your device doesn't support the server chosen algorithm. You can update the supported security provider as explained here: https://www.b4x.com/android/forum/threads/ssl-websocket-client.88472/page-2#post-560044 It will be simpler to use an Android 5+ device. Click to expand... Thanks. After using .InitializeAcceptAll, the httpjob works fine. According to your explanation the device does support the chosen algorithm. Should I look for an incorrect installation of the certificate? My device with android 8 and 9 are working fine with standaard library of OKHttp. I will try using the update of the security provider. Best regards, André
Erel B4X founder Staff member Licensed User Longtime User Oct 30, 2019 #4 You haven't provided enough information for us to help you. Where is the error message? Upvote 0
AHilberink Active Member Licensed User Longtime User Oct 30, 2019 #5 Erel said: You haven't provided enough information for us to help you. Where is the error message? Click to expand... Of course, sorry. The message is: ResponseError. Reason: javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. Best regards, André Upvote 0
Erel said: You haven't provided enough information for us to help you. Where is the error message? Click to expand... Of course, sorry. The message is: ResponseError. Reason: javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. Best regards, André
Erel B4X founder Staff member Licensed User Longtime User Oct 30, 2019 #6 The question in the first post and this error are not related. This error happens because the certificate authority is not recognized by the device. Upvote 0
The question in the first post and this error are not related. This error happens because the certificate authority is not recognized by the device.