topic Re: Mobile not allowing self-signed SSL Certs in Alfresco Archive

Mobile not allowing self-signed SSL Certs

msaffer — Thu, 05 Jan 2012 03:20:34 GMT

I am attempting to use an intranet web application within the Alfresco Mobile application on the iPad. The way I am currently going about this is to have a Microsoft Word document with a link to the web application stored in each site.This works fine if I try to initiate a connection with a fully-si

Re: Mobile not allowing self-signed SSL Certs

mikeh — Thu, 05 Jan 2012 08:13:12 GMT

Hello

Yes, we're aware of the issue. Please see: https://issues.alfresco.com/jira/browse/MOBILE-13

Also: https://forums.alfresco.com/en/viewtopic.php?p=120829#p120829

Thanks,
Mike

Re: Mobile not allowing self-signed SSL Certs

msaffer — Fri, 06 Jan 2012 00:44:33 GMT

Apologies for not finding this while searching the site. Thanks for the quick response!

Re: Mobile not allowing self-signed SSL Certs

pkrauer — Fri, 22 Mar 2013 08:52:28 GMT

Hi Mike,
the same issue appears on Android.
Is it planned to be fixed there as well?

Cheers,
Päng

Re: Mobile not allowing self-signed SSL Certs

gavinc — Fri, 22 Mar 2013 09:21:37 GMT

Hi Päng,

Yes, the 1.1 version of Android coming soon will address the self-signed certificate issue.

However, it will be done slightly differently than the iOS app i.e. not an in-app setting.

You will need to place a specific file with a specific name in a specific location on your device to enable the feature, this will be documented on the wiki when we release.

Regards,

Re: Mobile not allowing self-signed SSL Certs

pkrauer — Sun, 31 Mar 2013 20:00:49 GMT

Hi Gavin,
many thanks! I'm looking forward to get this new version!

Best regards,
Päng

Re: Mobile not allowing self-signed SSL Certs

pkrauer — Thu, 02 May 2013 11:27:05 GMT

Hi Gavin,
I just installed the new Version 1.1.0.114 this morning.

Where do I need to install the self-signed certificate to? Is there a documentation somewhere?

Best regards,
Patrick

Re: Mobile not allowing self-signed SSL Certs

mikeh — Thu, 02 May 2013 13:09:56 GMT

Hi Patrick

Apologies, we haven't published the wiki article yet. However, please find the instructions below:

Requirements:
You need a file explorer/manager installed in your device. You can find one in Google play Store with keywords like file explorer / file manager

Procedure:
<ul>
<li>With your file explorer : Go to the root folder of your sdcard. Generally the path looks like /sdcard or /mmt/sdcard . In recent version of Android it can also be : /storage/emulated/….

<li>Go to the following folder (or create this hierarchy if necessary): Android/data/org.alfresco.mobile.android.application/files

<li>Inside this folder create an empty file with a name like <hostname>.properties. For example if your server hostname is
192.168.1.1, the filename is 192.168.1.1.properties
example.alfresco.com, the filename is example.alfresco.com.properties
<li>When created, you can follow the default procedure to connect to your Alfresco server. NB : for security reason every first time a user try to connect to the server a notification is displayed. It alerts the SSL certificate validation is disabled.
</ul>

IMPORTANT: We highly recommend to use this solution only for testing/development purpose.

Re: Mobile not allowing self-signed SSL Certs

jm_pascal — Mon, 13 May 2013 18:47:32 GMT

Hello,

All informations are now available here : https://wiki.alfresco.com/wiki/Alfresco_Mobile_for_Android_:_Advanced_Setup_Guide

Re: Mobile not allowing self-signed SSL Certs

dynabix — Fri, 15 Aug 2014 17:07:40 GMT

In the new app for IOS setting the option to allow self-signed certificates seems to be gone again. Can it be re-added?

Greetz,
David

Re: Mobile not allowing self-signed SSL Certs

mikeh — Thu, 04 Sep 2014 08:55:14 GMT

There's a discussion in another thread about this, but briefly: it was removed due to customer request regarding security concerns. It won't be reinstated in the same way, but I've had initial thoughts on how self-signed certificates might be supported in the future.

Thanks,
Mike