Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-69185

Officially provide support for internal and external base url for JIRA

XMLWordPrintable

    • 151
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      There is currently no official way to configure JIRA with two url and it is very common for organizations to have one internal and one external url.

      It is currently only possible to configure one baseurl and this is mentioned in our documentation :

      1. https://confluence.atlassian.com/upm/diagnosing-base-url-configuration-problems-273875734.html
      2. https://confluence.atlassian.com/adminjiraserver/configuring-jira-application-options-938847824.html

      The base URL of this Jira installation. You can only configure Jira to respond to a single URL and this setting must match the URL that your users request for accessing your Jira instance. You cannot (for example) have a different hostname or URL for internal and external users.

      Suggested Solution

      Provide the functionality and official documentation on how to configure JIRA with internal and external or more than one url.

      Notes

      While one can configure multiple Tomcat connectors with different URLs, due to the nature of our current OAuth implementation signing requests with the base URL setting ( see https://docs.atlassian.com/DAC/javadoc/applinks/3.6.1/reference/com/atlassian/applinks/core/auth/oauth/RequestUtil.html ), using a different URL other than the base url will break integrations relying on OAuth for authentication

          Form Name

            [JRASERVER-69185] Officially provide support for internal and external base url for JIRA

            Carol Li added a comment -

            Hello,  we need this functionality too, is there any updates on this topic?

             

            Thanks.

            Carol Li added a comment - Hello,  we need this functionality too, is there any updates on this topic?   Thanks.

            Jakobus Schürz added a comment -

            We also run Jira behind a portal solution, where users can come from different domains to the same Jira instance.
            So we need a possibility to render gadgets and urls with the url, where the user came from.

            This are more than 2 different urls.

            Here is no way, to run Jira directly on the internet with only 1 url.

            Jakobus Schürz added a comment - We also run Jira behind a portal solution, where users can come from different domains to the same Jira instance. So we need a possibility to render gadgets and urls with the url, where the user came from. This are more than 2 different urls. Here is no way, to run Jira directly on the internet with only 1 url.

            Ilyas Kucukcay added a comment -

            This is an ongoing demand for most business units as it's impacting our ability to expand the adoption of Jira in our organization. Without proper setup, we are not able to provide reliable support and commitment to integrate our instance to other third-party systems. Please prioritize this as much as you can. Thank you very much. 

            Ilyas Kucukcay added a comment - This is an ongoing demand for most business units as it's impacting our ability to expand the adoption of Jira in our organization. Without proper setup, we are not able to provide reliable support and commitment to integrate our instance to other third-party systems. Please prioritize this as much as you can. Thank you very much. 

            Antreas Solou added a comment -

            Hello, 

            We have the same issue for so long now. We need this functionality. 

            KR,

            Antreas Solou added a comment - Hello,  We have the same issue for so long now. We need this functionality.  KR,

            John Wehrle added a comment -

            We definitely need this feature. Basic Jira functionality works OK via our external URL over a reverse proxy configuration, but our Dashboards are unusable, and we can't create extranet-only dashboards due to the conflict between external URL and the internal base URL.

             

            John Wehrle added a comment - We definitely need this feature. Basic Jira functionality works OK via our external URL over a reverse proxy configuration, but our Dashboards are unusable, and we can't create extranet-only dashboards due to the conflict between external URL and the internal base URL.  

              Unassigned Unassigned
              astephen@atlassian.com Adrian Stephen
              Votes:
              113 Vote for this issue
              Watchers:
              100 Start watching this issue

                Created:
                Updated: