Alfresco / alfresco-ios-app

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Unable to connect to repository with client certificate

onno182 opened this issue · comments

Connecting to a repository with a client certificate does not seem to work on the initial connection. The following error is displayed.

2018-12-08 12:45:06.638186+0100 AlfrescoApp[43798:7438347] [BoringSSL] boringssl_context_alert_callback_handler(3718) [C13.1:2][0x7f86abc763f0] Alert level: fatal, description: protocol version 2018-12-08 12:45:06.638295+0100 AlfrescoApp[43798:7438347] [BoringSSL] boringssl_session_errorlog(224) [C13.1:2][0x7f86abc763f0] [boringssl_session_handshake_incomplete] SSL_ERROR_SSL(1): operation failed within the library 2018-12-08 12:45:06.638400+0100 AlfrescoApp[43798:7438347] [BoringSSL] boringssl_session_handshake_error_print(205) [C13.1:2][0x7f86abc763f0] 140216386240376:error:1000042e:SSL routines:OPENSSL_internal:TLSV1_ALERT_PROTOCOL_VERSION:/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl_Sim/boringssl-109.220.4/ssl/tls_record.cc:586:SSL alert number 70 2018-12-08 12:45:06.638499+0100 AlfrescoApp[43798:7438347] [BoringSSL] boringssl_context_get_error_code(3575) [C13.1:2][0x7f86abc763f0] SSL_AD_PROTOCOL_VERSION 2018-12-08 12:45:06.639534+0100 AlfrescoApp[43798:7438347] CFNetwork Diagnostics [3:143] 12:45:06.639 { TCP Connection Failed: (null) Connection ID: 13 Error Code: -9836 Error: } [3:143] 2018-12-08 12:45:06.63962

However, it is possible to get client certificates working when doing the following steps, which leads me to think it is a bug.

  1. Connect to the repository without client certificates (deactivating client certificate authentication in Apache)
  2. Adding the client certificate in the menu once connected to the repository.
  3. Reconnecting to the repository (activating client certificate authentication in Apache)