Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can't connect mobile confluence app to internal confluence setup

Kevin Pechin July 11, 2018

Hi,

We have an internal only confluence install on our network running on port 7443. While my android device is on wifi at our institution I can use a browser to connect and log in (via a cas plugin) and everything works fine. When I try the confluence app, I get the error:
"Can't connect to your site. This could be because the URL is wrong, you need to use a VPN, or Confluence is unavailable"

Is there a special url I have to use or does this just not run on non standard ports?

The SSL certificate is a valid wildcard certificate that we use on many public facing sites.

The confluence mobile plugin is enabled and we are running confluence server v6.8.2.

Any ideas on where I can start troubleshooting this? Thanks!

-Kevin

1 answer

0 votes
Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 11, 2018

Hey Kevin,

The app requires TLS 1.2 which might not be in the HTTPS connector if you're coming from an older version of Confluence. The requirement is documented here if you want to take a peek.

Can you double-check this is enabled in your server.xml, or post the HTTPS connector portion? sslProtocols and sslEnabledProtocols are the directives to check.

Thanks,
Daniel

Kevin Pechin July 11, 2018

Hi Daniel,

Thanks for your response.  I double checked and I did have 1.2 enabled, but I also had 1.1.  As a test I just removed all options except for 1.2, restarted and tested again with the same result.  So now the server.xml looks like this:

sslProtocols="TLSv1.2"
sslEnabledProtocols="TLSv1.2"

Is there a particular cipher set I should be using as well or something else I can look at?  I have the following enabled:

ciphers="TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_RC4_128_MD5,TLS_RSA_WITH_RC4_128_SHA"

Thanks,

-Kevin

Sven Laanela
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 12, 2018

Hi Kevin,

When you are talking about CAS plugin, are you referring to some kind of single-sign on infrastructure that if set up for that confluence instance? (such as JASIG CAS?)

This error indicates that the mobile app cannot connect to /server-info.action on the confluence server instance. One of the reasons this might happen is that there is a catch-all filter (with url-pattern /*) added to confluence in web.xml that intercepts calls to all urls (including /server-info.action) and causes a redirect to some authentication page/mechanism. Unfortunately this breaks the mobile app as the app needs to access information from that url before being able to continue with the login process.

Do you know if there is any filter added to the web.xml for confluence that could cause this?

Looking forward to your reply,

-Sven 

Kevin Pechin July 13, 2018

Hi Sven,

You called it.   Yes the CAS plugin is for performing single sign on.  We are using an old CAS client since no one really supports CAS and Confluence.  You are also correct that there are filters in the web.xml mapping "/*" .  Do you know what the full path to "/server-info.action" is?  I tried hitting that while authenticated and I get a broken link.  Maybe I can add an exception to the filter to allow this url.  

Are you aware of any SSO plugins that would still allow us to use the mobile app out of the box?  I see there are a few SAML addons. 

Thanks again for your time and information!

-Kevin

Sven Laanela
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 16, 2018

Hi Kevin,

The server-info.action is queried from the root of the app deployment context. So, for example, if the full path to your confluence is https://some.host/confluence, then the full path to server-info.action would be https://some.host/confluence/server-info.action.

The mobile app does a HTTP HEAD call to that url and expects to see "mobile-plugin-enabled: true" as well as other "mobile-" related info in the response headers. Note that it is expected for the request itself to return a 404.

Let me know if this helped, 

-Sven

Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 17, 2018

As for the second question - I have personal experience with the resolution.de authored SAML plugin. Worked well with ADFS! The other SAML offerings from other vendors are pretty similar. Atlassian also natively supports SAML in the Data Center offering of Confluence if that winds up being something you consider.

Kevin Pechin July 23, 2018

Thanks Sven and Daniel, I appreciate both responses.  I'm going to attempt to write a filter to exclude /server-info.action head requests or see if I can find the source to the original CAS filter and add the exception there.  If that doesn't work out I'll definitely check out the SAML plugin.   Have a great day.

-Kevin

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events