Using Jira Mobile over Application proxy

[Mattias Kallvi]

We are running our Jira behind firewalls. Resently we made it reachable from the internet, without VPN, through an Application Proxy in Azure. This works just fine when using a browser. However, this doesn't work with Jira Mobile. Anyone who knows if this should be possible? And if not, is it on any roadmaps?

[Mirek]

Hi @Mattias Kallvi 

Are you sure that you use correct Jira mobile apps (there are two for Cloud and Server) and using Jira 8.1?

[Mattias Kallvi]

Yes, I use the Jira Server version of the app. The server behind the Application Proxy is running Jira 7.10.2 but in these cases I should get a warning about the Jira version. I have verified this on other Jira servers that can be reached directly from the Internet without an application proxy. In my case I can't even reach the Jira server URL.

I Think that the app can't handle the Azure AD Authentication that you will be prompted with. My guess is that the app expect to reach the Jira sign-in page directly. Maybe it should be an improvment suggestion.

[Mirek]

In order to use Jira Server you need to have Jira 8.1.

Below is all info that you need including VPN connection.. etc.

https://confluence.atlassian.com/jirasoftwareserver/jira-software-mobile-app-966063511.html

[Mattias Kallvi]

Yes, I know that I need Jira 8.1 to be able to use Jira server app. But when running Jira behind an application Proxy I can't even access the URL in the app (works fine in browser). Some findings regarding the Jira server app:

• Jira reachable from the internet (no application Proxy in Azure), Jira-version 7.2.8. Here I am prompted with an warning saying that I need to upgrade. Works as intended.
• Jira that is behind an Application Proxy in Azure, Jira-version 7.10.2. Here I get an error message saying "Can't connect to your site". 

My guess is that the Jira app cannot handle sites that are behind an application Proxy in azure. Looking for verification on this. And if so, I Think that it would be a great improvment  to be able to use that solution. No need for VPN.

[Mirek]

Did you look at this KB?

https://confluence.atlassian.com/jirakb/can-t-connect-to-your-site-error-in-the-jira-server-mobile-app-954244697.html

[Mattias Kallvi]

Yes, I've read that one. Once I have a VPN up and running on the phone it works fine. But the Company I work at is trying to move away from VPN on mobile and instead use application Proxy. As mentioned, it works fine when using a browser but the mobile app doesn't seem to be able to handle it. I Think I will create an Improvment suggestion.

[scott_boisvert]

@Mattias Kallvi Were you able to solve this? I'm working through a similar issue.

[Mattias Kallvi]

No, I was not able to solve this. When using a VPN connectin it was no problem. But when we tried to use the Application Proxy in Azure I was unable to connect. I think it is because you get two authentications, first the one in Azure and then the Jira-authentication, and the mobile app can't handle the first one.

If you ask me I think the best solution would be not to have mobile app at all. Istead have a responsive Jira webpage solution.

I will not investigate this further since I have moved on to another company... it's someone elses problem now :-) However, if you solve this please let me know.

[alexandre.cardoso]

Does Atlassian mobile applications Jira Server and Confluence Server support ADAL and specifically the MFA handshake process?

ADAL - Azure Active Directory Authentication Library

[scott_boisvert]

@alexandre.cardoso I'm hoping so. That's what we're looking to do. With everything going in the world, we haven't had a chance to explore this yet.

[Jason Freeman]

I really doubt the Jira app supports Modern Authentication, which is required by Azure (and Google, for what it's worth).

Actually, Jira itself doesn't support it, either. The difference, however, is that you can at least add that capability via addons. I doubt the Jira app supports addons that fundamentally change the logon process, but I could be wrong.