we need this functionality for both Bitbucket and confluence. 

Created: 03/Feb/2017 10:17 PM = low chance

We really need this functionality

+1

+1

"Most people could do it under load balancing or DMZ but due to many security issues people want to protected it under some source or reverse proxy mean hidden the URL by an alias or wrapper under a different URL.  In this case, people inside the company network will use the real URL but people outside the company will have to use it under a different URL from a restricted network outside the intranet.  DNS mapping can't resolve this issue"

That's my case. Could Jira implement this features as soon as possible?

We have a similar situation as well.  

We do not have a DMZ presence.  Our application is internal. 

However with all the mobile accessibility options today, we wanted our users to be able to respond to tickets outside business hours and off network to update approvals as well as transition issues without having to log onto the company network via VPN or citgo.

We decided to use Azure as a proxy and configure an Enterprise application.

This works somewhat..  as users can access the Azure proxy off network and login with their domain account then Azure passes them inside to the application, which then again prompts for a login, but then we get the gadget errors and marketplace access issues because the Azure proxy URL does not match the base URL.

We don't want a one way only option.  (changing the base URL so everyone has to go through Azure).  It doesn't make sense for on network users to login outside to get back inside.  

We want in office users to be able to access via base URL and the external users access via Azure.

I have tried adding the proxy to the server.xml file or even in java registry parameters but this has no impact.

Microsoft recommends a 

split-brain DNS approach.  Then we can configure 2 Idps (enterprise apps on Azure)

Reference:

https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/application-proxy-configure-custom-domain

 However, we do not want to have to manage external and internal certificates and we don't want a public DNS.

We are also in this situation where we want to setup multiple base url or else option where we can use different url in email notifications.

We would greatly appreciate it there could be multiple URLs, such as an internal URL and an external URL.

We also have a requirement internal / external URLs.

It'd be nice if one Jira and service desk would support two URLs.  I'm moving from one domain to another and because I have to hard code the URL in the product it doesn't support both well.  Example of what I'm doing:

going from: helpdesk.trusted.vhe.example.net

going to: helpdesk.vhe.example.net

I can easily support both but when I log in using just https://helpdesk.vhe.example.net I get errors.  I'm going to reconfigure so it'll redirect to the trusted but I'd be nice if it could work with both until I can cut over to the shorter URL

We have a similar situation where Jira may need to support multiple URLs. For example, we have public facing URL as www.pub-jira.com and another for private/internal URL as www.priv-jira.com. 

Using reverse proxy we would like to utilize two different URLs but at this moments that is not possible.

Thanks 

It will be great if JIRA can support multiple urls. So internal users can use regular urls and when same users are outside of network, they can access Jira with proxy url , I.e. on mobile devices...

Hi, 

When this functions could be deployed in official version?

We're using diff. domain for in/external, so need to use this function.

Thanks

Eric

David, nope, what you said is not the case and not even close to the issue.  If you read a lot out there, people has secure issue need to be resolved,  We need to be able to run the Jira in the Intranet and also outside the intranet but restricted network for customers access.  Most people could do it under load balancing or DMZ but due to many security issues people want to protected it under some source or reverse proxy mean hidden the URL by an alias or wrapper under a different URL.  In this case, people inside the company network will use the real URL but people outside the company will have to use it under a different URL from a restricted network outside the intranet.  DNS mapping can't resolve this issue, we already tried everything.  Thanks.

By the way, I think the confusion is from my part.  I should have generated a different issue for this but since I found that it should be a same related change for the URL so I try to put it here too instead of open it in a separate issue.

I can't imagine Atlassian even entertaining this idea. 

If you want to have different URLS or domains point to the same Jira instance, but to a specific Project Board or Filter, you can do that through your DNS mappings (basically a forward). 

A lot of people interact with Jira through Dashboards, Reports, Filters, etc that are not necessarily project specific. There are also multi-tenant projects where things are split up by board, component, security level, etc. How would you accomplish that via a URL?

I would like this functionality added to Jira.  If Atlassian can add this, I think it will interested a lot more customers.  We plan to retired a lot of others applications and just use Jira; however, due to this limitation, we could not get rid off the other application because of their benefit is to be able to serve in many different URLs (internal/external).   Smart web app should always consider this features because it is a requirement for many companies.

+1

+100500

+1

+1

Please add this!

+ 4294967296

+1

it would be great to manage sites

My case is that I have a path like

• https://company.com/jira/common

and I plan to change it to

• https://jira.company.com/

But the old address should also work for backwards compatibility.

This would be very usefull future