nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Unable to logon in Alfresco Community Server after upgrading iOS Alfresco App to version 2.0

jeesee

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 tried to reconfigure the connection on the iPhone, but after delete de connection to my Alfresco server I can't configure a new one:

Save Account
Failure to authenticae. Check your
account settings with your system
administrator.

Is something changed in the new iOS app?

How can I configure it to connect with my Alfresco server?

Server settings:
Username: jeesee
Password: xxxxx <- I'm sure it's right!
Hostname: My Alfresco Server .nl
Description
HTTPS: On

Sync files: Off
Port: 8443
Service Document: /alfresco/service/cmis
Client Certificate:

Please Help!

Find more posts tagged with

Comments

marc_dubresson

Hi Jeesee,

The team suggests that the sevice document should simply be: /alfresco

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.

Regards,

jeesee

Thank you Marc for your reply.
I changed the Service Document, but still the Failure to authenticate-error..
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..

mikeh

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.

If that is the case, you'll either need to provision the correct SSL certificate, or use an HTTP connection.

Thanks,
Mike

jeesee

Thank you Mike, that can be the issue..
But how can I configure a correct SSL certificate to my Alfresco Tomcat installation? Can it be a self-signed certificate?

lucasolferino

I have the same problem, but in my case I use a Reverse Proxy Apache, with a validi certificate suggestions?

thank you

ulus

Hello,
after upgrade to new iOS App authentication failture. Alfresco is behind nginx reverse proxy.
SSL <> nginx (valid Startcom Cert.) <> tomcat:8080 - Alfresco 4.2c
Worked without problems before.

Regards

mikeh

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.

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).

Thanks,
Mike

ulus

Perfect.
Thx a lot.

Best Regards

vrugginkj

Hello,

We've got a valid certificate from UserTrust Legacy.

Since the update to Mobile 2.0, w've the same problem.
Our technical consultant thinks that the wildcard might be the problem (*.ourdomain.xx)

Any idea ?

PS, The application FreshDocs from ZIA still works fine…

Alfresco 4.2.e

x1m

Hi ulus,

What changes did you make to make it work with nginx?

Best Regards,

jack_chuong

Hi Mike,
I'm using Alfresco Community 5.0.a on Centos 6.4 64 bit and I have similar problem with iOS Alfresco App version 2.0
We only use HTTP, my user can use Alfresco by URL http://alfresco.mydomain.com/alfresco or http://alfresco.mydomain.com/share from internal and external, request come to port 80 is redirected to 8009 by mod_jk, this is my server.xml configuration:

    <Connector port="8080" URIEncoding="UTF-8" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" maxHttpHeaderSize="32768" />

    <Connector port="8009" URIEncoding="UTF-8" protocol="AJP/1.3" redirectPort="8443" />

    <Connector port="8443" URIEncoding="UTF-8" protocol="org.apache.coyote.http11.Http11Protocol" SSLEnabled="true"
               maxThreads="150" scheme="https" keystoreFile="/opt/alfresco-5.0.a/alf_data/keystore/ssl.keystore" keystorePass="kT9X6oe68t" keystoreType="JCEKS"
 secure="true" connectionTimeout="240000" truststoreFile="/opt/alfresco-5.0.a/alf_data/keystore/ssl.truststore" truststorePass="kT9X6oe68t" truststoreType="JCEKS"
               clientAuth="want" sslProtocol="TLS" allowUnsafeLegacyRenegotiation="true" maxHttpHeaderSize="32768" />
‍‍‍‍‍‍‍‍‍‍‍‍

What should I do to make it work with iOS Alfresco App to version 2.0 ?
Everything works fine with Alfresco Android App
Server settings:
Username: jack.chuong
Password: xxxxx
Hostname: alfresco.mydomain.com
Description
HTTPS: Off

Sync files: Off
Port: 80
Service Document: /alfresco
Client Certificate:

mikeh

Looks like you just need to add the proxyName and proxyPort attributes, i.e. proxyName="alfresco.mydomain.com" and proxyPort="80"

Thanks,
Mike

jack_chuong

Hi Mike,
I tried but it doesn't work, error popup when I try to login by iOS Alfresco App : "Failure to authenticate. Check your account settings with your system administrator"

this is my server.xml configuration

    <Connector port="8080" URIEncoding="UTF-8" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" maxHttpHeaderSize="32768"
               proxyName="alfresco.mydomain.com" proxyPort="80" />
    <Connector port="8009" URIEncoding="UTF-8" protocol="AJP/1.3" redirectPort="8443" />

    <Connector port="8443" URIEncoding="UTF-8" protocol="org.apache.coyote.http11.Http11Protocol" SSLEnabled="true"
               maxThreads="150" scheme="https" keystoreFile="/opt/alfresco-5.0.a/alf_data/keystore/ssl.keystore" keystorePass="kT9X6oe68t" keystoreType="JCEKS"
 secure="true" connectionTimeout="240000" truststoreFile="/opt/alfresco-5.0.a/alf_data/keystore/ssl.truststore" truststorePass="kT9X6oe68t" truststoreType="JCEKS"
               clientAuth="want" sslProtocol="TLS" allowUnsafeLegacyRenegotiation="true" maxHttpHeaderSize="32768" />
‍‍‍‍‍‍‍‍‍‍‍‍

Or I need to add the proxyName and proxyPort attributes into Connector port="8009" ?

mikeh

I've not tried with the mod_jk method. Did you try adding the two proxy attributes to the port 8009 connector?

You can manually check the URLs are being generated correctly by inspecting the response from

http://alfresco.mydomain.com/alfresco/api/-default-/public/cmis/versions/1.0/atom
‍‍‍

Thanks,
Mike