<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0 in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285113#M238243</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Just add the root CA certificate (the one you used to generate the self-signed certs with) to your user's devices and they'll connect fine. This also works with the client certificate implementation that's in the app.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We can't selectively allow end users to switch off SSL validation for the reasons I've outlined elsewhere in this thread. I'm sorry that doesn't match your particular set of IT policies.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Oct 2015 12:55:57 GMT</pubDate>
    <dc:creator>mikeh</dc:creator>
    <dc:date>2015-10-14T12:55:57Z</dc:date>
    <item>
      <title>Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285085#M238215</link>
      <description>I'm having a problem after (automatic) upgrading the Alfresco App today.Yesterday with the "old" Alfresco App (black icon) on my iPhone and iPad it all works fine.Today I started the iPad app (it was automatically upgraded on both my iPhone and iPad to the 'white' icon) I receive a Session Error.I t</description>
      <pubDate>Thu, 10 Jul 2014 08:56:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285085#M238215</guid>
      <dc:creator>jeesee</dc:creator>
      <dc:date>2014-07-10T08:56:23Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285086#M238216</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Jeesee,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The team suggests that the sevice document should simply be: /alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I also wanted to point out for the benefit of everyone that if you have an issue getting back on your cloud account after the update you can simple swipe the account name left to delete it and add it again.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jul 2014 09:14:58 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285086#M238216</guid>
      <dc:creator>marc_dubresson</dc:creator>
      <dc:date>2014-07-10T09:14:58Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285087#M238217</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thank you Marc for your reply.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I changed the Service Document, but still the Failure to authenticate-error..&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;It also isn't on my cloud account, but on the connection to an Alfresco Community Edition 4.2f server, which worked perfectly before the app-update..&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jul 2014 13:41:51 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285087#M238217</guid>
      <dc:creator>jeesee</dc:creator>
      <dc:date>2014-07-10T13:41:51Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285088#M238218</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I notice you're connecting directly to Tomcat (presumably?) on port 8443. Does that have a valid SSL certificate assigned to it? We no longer allow SSL connections with untrusted certificates due to customer concerns fed back to us from the previous app.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If that is the case, you'll either need to provision the correct SSL certificate, or use an HTTP connection.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jul 2014 13:48:12 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285088#M238218</guid>
      <dc:creator>mikeh</dc:creator>
      <dc:date>2014-07-10T13:48:12Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285089#M238219</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thank you Mike, that can be the issue..&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;But how can I configure a correct SSL certificate to my Alfresco Tomcat installation? Can it be a self-signed certificate?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jul 2014 13:50:55 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285089#M238219</guid>
      <dc:creator>jeesee</dc:creator>
      <dc:date>2014-07-10T13:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285090#M238220</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;No, sorry - it's self-signed certificates (and expired certificates) that we explicitly disallow. The "allow untrusted SSL" user preference was quite unpopular and so we didn't reimplement it in 2.0. Besides, if it's self-signed, there's very little benefit so you might as well be using HTTP anyway.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It's fairly easy to purchase and install a certificate for your Tomcat server (or Apache web server; I have a test Apache server that proxies to a development repo setup with SSL).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jul 2014 18:33:37 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285090#M238220</guid>
      <dc:creator>mikeh</dc:creator>
      <dc:date>2014-07-10T18:33:37Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285091#M238221</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have the same problem, but in my case I use a Reverse Proxy Apache, with a validi certificate suggestions? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thank you&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 07:34:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285091#M238221</guid>
      <dc:creator>lucasolferino</dc:creator>
      <dc:date>2014-07-11T07:34:30Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285092#M238222</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Make sure your Tomcat Connector has the appropriate proxy attributes added, here's mine as an example:&lt;/SPAN&gt;&lt;BR /&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;Connector port="8090" protocol="HTTP/1.1" &lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; connectionTimeout="20000" &lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; redirectPort="8443" URIEncoding="UTF-8"&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; scheme="https"&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; proxyName="alfresco.mikehatfield.net" proxyPort="443" /&amp;gt;&lt;BR /&gt;&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;This ensures CMIS generates the correct absolute URLs in the responses.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 17:46:00 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285092#M238222</guid>
      <dc:creator>mikeh</dc:creator>
      <dc:date>2014-07-11T17:46:00Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285093#M238223</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Could I ask why you need a self-signed certificate to access your server? Perhaps that will help us understand the requirements.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Jul 2014 17:48:23 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285093#M238223</guid>
      <dc:creator>mikeh</dc:creator>
      <dc:date>2014-07-11T17:48:23Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285094#M238224</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I've got the same problem with a cacert certificate where the root certificate is correct deployed in the iOS profile. Every other service is working except Alfresco for iOS 2.0!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jul 2014 06:55:38 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285094#M238224</guid>
      <dc:creator>pflaeging</dc:creator>
      <dc:date>2014-07-15T06:55:38Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285095#M238225</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;When you say "every other service" - is that other third party apps, or just the built-in iOS apps? I've definitely heard of limitations regarding non-Apple apps and custom root certificates. I had success testing with a Comodo certificate (and with local CA-generated client certificates)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jul 2014 20:46:11 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285095#M238225</guid>
      <dc:creator>mikeh</dc:creator>
      <dc:date>2014-07-15T20:46:11Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285096#M238226</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Some more quoted text:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;blockquote&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;No, sorry - it's self-signed certificates (and expired certificates) that we explicitly disallow. The "allow untrusted SSL" user preference was quite unpopular and so we didn't reimplement it in 2.0. Besides, if it's self-signed, there's very little benefit so you might as well be using HTTP anyway.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It's fairly easy to purchase and install a certificate for your Tomcat server (or Apache web server; I have a test Apache server that proxies to a development repo setup with SSL).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;/blockquote&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I have a dynamic ip-adres which is provided by my isp. So a signed ssl certificate would not work because of the ip changes. Besides not to offend you, but do you know the difference between HTTPS en HTTP? A self-signed certificate can be accepted so that i decide it's safe. Then i can use the https connection and all my communication will be encrypted. Using http i lose this ability and even the login / password data will be send unencrypted.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So yes i would like to use https but not pay $60 for a ssl certificate.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But what is the reason you would not implement a feature which you already had?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jul 2014 07:12:38 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285096#M238226</guid>
      <dc:creator>gerardh</dc:creator>
      <dc:date>2014-07-17T07:12:38Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285097#M238227</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;after upgrade to new iOS App authentication failture. Alfresco is behind nginx reverse proxy.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;SSL &amp;lt;&amp;gt; nginx (valid Startcom Cert.) &amp;lt;&amp;gt; tomcat:8080 - Alfresco 4.2c&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Worked without problems before.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jul 2014 20:42:07 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285097#M238227</guid>
      <dc:creator>ulus</dc:creator>
      <dc:date>2014-07-17T20:42:07Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285098#M238228</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'm unclear as to why you can't assign an SSL certificate to your particular setup… TLS has supported IP address changes for a number of years now via the SNI extension [1]; supported by all browsers except Android 2.x and MSIE on Windows XP. There are many services that support dynamic DNS for people such as yourself who cannot obtain a static IP address, &lt;/SPAN&gt;&lt;A href="http://www.dtdns.com/" rel="nofollow noopener noreferrer"&gt;http://www.dtdns.com/&lt;/A&gt;&lt;SPAN&gt; is just one.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;So yes i would like to use https but not pay $60 for a ssl certificate.&lt;/BLOCKQUOTE&gt;&lt;SPAN&gt;Personally I think it's a small price to pay for security compared to the value you're getting from an Alfresco repository and mobile apps. We may just need to agree to differ on that one.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;But what is the reason you would not implement a feature which you already had?&lt;/BLOCKQUOTE&gt;&lt;SPAN&gt;That's a fair question. The previous iOS apps were based on code that one of our partners (Zia) originally wrote. Whilst it gave us a huge boost in getting a mobile app to market, the architecture &amp;amp; design of the app wasn't quite to our liking, including inheriting some features we wouldn't necessarily have added by choice. One of those was giving the end user the ability to switch off SSL validation. We had some very strong feedback from some of our larger enterprise customers that this was extremely undesirable. Fast-forwarding to our iOS 2.0 app, this was a complete re-write on top of ObjectiveCMIS and the Alfresco iOS SDK. When choosing what features to prioritise (or exclude) we looked back at all the customer feedback and that one stood out particularly. Hence why it's not in the app today.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;On a more positive note, I have been actively thinking of how we can support self-signed certificates in the future. The SDK already allows this as a runtime parameter, so it's just our "out of the box" app that enforces the policy. Clearly we need an Alfresco admin to allow untrusted connections via some policy, but it's somewhat of a "chicken and egg" problem as you need the app to connect to the repository in order to retrieve the policy setting. As I said, I have some ideas as to how this could work for all parties, but I can't guarantee when the store app will allow it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;[1] &lt;/SPAN&gt;&lt;A href="http://en.wikipedia.org/wiki/Server_Name_Indication" rel="nofollow noopener noreferrer"&gt;http://en.wikipedia.org/wiki/Server_Name_Indication&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;P.S. Yes, I'm fully aware of the difference between http and https, but thanks for checking &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jul 2014 21:12:00 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285098#M238228</guid>
      <dc:creator>mikeh</dc:creator>
      <dc:date>2014-07-17T21:12:00Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285099#M238229</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Please see my comment above about the Tomcat connector. You'll likely need to proxy to a separate connector (i.e. on a different port) that has the proxy attributes set.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Note: The main reason everyone is having problems is due to the CMIS endpoint change from our webscript CMIS implementation (at /service/cmis) to the more performant OpenCMIS implementation (/cmisatom).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jul 2014 21:16:02 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285099#M238229</guid>
      <dc:creator>mikeh</dc:creator>
      <dc:date>2014-07-17T21:16:02Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285100#M238230</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Perfect.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thx a lot.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best Regards&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Jul 2014 07:51:38 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285100#M238230</guid>
      <dc:creator>ulus</dc:creator>
      <dc:date>2014-07-18T07:51:38Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285101#M238231</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thank you, your solution work.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Luca&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jul 2014 07:31:12 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285101#M238231</guid>
      <dc:creator>lucasolferino</dc:creator>
      <dc:date>2014-07-23T07:31:12Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285102#M238232</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks for the follow-up confirmation Luca.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Mike&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 23 Jul 2014 08:12:12 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285102#M238232</guid>
      <dc:creator>mikeh</dc:creator>
      <dc:date>2014-07-23T08:12:12Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285103#M238233</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;We've got a valid certificate from UserTrust Legacy. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Since the update to Mobile 2.0, w've the same problem. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Our technical consultant thinks that the wildcard might be the problem (*.ourdomain.xx)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any idea ?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;PS, The application FreshDocs from ZIA still works fine…&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Alfresco 4.2.e&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Jul 2014 07:12:00 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285103#M238233</guid>
      <dc:creator>vrugginkj</dc:creator>
      <dc:date>2014-07-24T07:12:00Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285104#M238234</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi ulus,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What changes did you make to make it work with nginx?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best Regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Aug 2014 22:13:08 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/unable-to-logon-in-alfresco-community-server-after-upgrading-ios/m-p/285104#M238234</guid>
      <dc:creator>x1m</dc:creator>
      <dc:date>2014-08-04T22:13:08Z</dc:date>
    </item>
  </channel>
</rss>

