Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-24274

Allow Support for Multiple Domains through Purchasing of Multiple Licenses

    • We collect Confluence 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.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Via the tickets I can see Atlissian does not want customers using one instance of Confluence for multiple domains.

      Please consider the scenario where Enterprise customers would be willing to pay for this feature via some kind of licensing model.

      I am in talks with a large Bank on CMS/Wiki solutions beyond SharePoint. I brought Confluence up but the big concern is not being able to use multiple domains. The second is no support for virtualized cluster, but I can deal with that creatively.

      Hosted solutions are not options due to the sensitivity of the data. Starting on the IT side,

      https://webcash.bank.com
      https://trade.bank.com

      Would point load different spaces based on the domain name. Each space should not have awareness of the other. I know I can simulate this via Apache redirects, Virtual Hosting and removing the Dashboard link... but they want simplicity and some divisions are very territorial.

      Infrastructure costs are very very high (requirements for redundancy, DR, networking, staff to monitor the systems, ect.. ect..) so they would have no issue paying for additional licensing for this feature.

      I can see that to support this feature, Confluence simply needs to stop hard coding the base url. Instead, allow us to unlock more base urls if we purchases some kind of domain license and set corresponding "Site Homepage" urls with an option to remove the Dashboard link.

      Please consider this as an option for all your products provided Atlissian is targetting the Enterprise market.

            [CONFSERVER-24274] Allow Support for Multiple Domains through Purchasing of Multiple Licenses

            master added a comment -

            Our confluence is set-up and working well with an internal domain name.  Currently we have a requirement to allow external partners and our own users to access our confluence instance using a public domain so that we can share our resources with our partners and allow users to access our site securely when they are out of the office.  It is common that the public domain is configured a different name from the internal domain so as to avoid confusion and also to provide better access control.  For this purpose, I set up 2 web-servers to act as reverse proxy to connect to the confluence tomcat application server.  After disabling the checking on the base URL, things work fine when accessing from both sites, but I was told that this is not the recommended configuration.  But I feel that Atlassian has to provide a mechanism for multiple domains to connect to it as we are following IT security and configuration best practices.  Limiting the use to 1 domain seriously handicap the potential of Confluence and Jira to cater to a lot of different use cases and scenarios especially when relating to IT Security and Configuration Management needs from an IT infrastructure standpoint.

            master added a comment - Our confluence is set-up and working well with an internal domain name.  Currently we have a requirement to allow external partners and our own users to access our confluence instance using a public domain so that we can share our resources with our partners and allow users to access our site securely when they are out of the office.  It is common that the public domain is configured a different name from the internal domain so as to avoid confusion and also to provide better access control.  For this purpose, I set up 2 web-servers to act as reverse proxy to connect to the confluence tomcat application server.  After disabling the checking on the base URL, things work fine when accessing from both sites, but I was told that this is not the recommended configuration.  But I feel that Atlassian has to provide a mechanism for multiple domains to connect to it as we are following IT security and configuration best practices.  Limiting the use to 1 domain seriously handicap the potential of Confluence and Jira to cater to a lot of different use cases and scenarios especially when relating to IT Security and Configuration Management needs from an IT infrastructure standpoint.

            So in 2011, there was no view to fix this in the near term. We're now into Q3 of 2015, Atlassian is promoting that they're supporting enterprise customers. So often, the view of enterprise is, we just do a lot of the same things. For us, enterprise is 300+ companies, centrally managed from an IT point of view, throughout every market in the world, working together whenever we can, but also with our own branding. We have centralised documentation and processes (HR, finance, compliance etc), we have a single installation, however as we promote the tools throughout the rest of our companies, they love the concept, however not being able to have their domains used in accessing the systems. Would be great to hear there is something to support this on the near roadmap.

            Craig Castle-Mead added a comment - So in 2011, there was no view to fix this in the near term. We're now into Q3 of 2015, Atlassian is promoting that they're supporting enterprise customers. So often, the view of enterprise is, we just do a lot of the same things. For us, enterprise is 300+ companies, centrally managed from an IT point of view, throughout every market in the world, working together whenever we can, but also with our own branding. We have centralised documentation and processes (HR, finance, compliance etc), we have a single installation, however as we promote the tools throughout the rest of our companies, they love the concept, however not being able to have their domains used in accessing the systems. Would be great to hear there is something to support this on the near roadmap.

            Jirong Hu added a comment -

            So what's the solution to support multiple domain users?

            We want to integrate SVN with JIRA, and SVN can support multiple domains and we all use LDAP for authentication. Now what shall we do with JIRA?

            Thanks
            Jirong

            Jirong Hu added a comment - So what's the solution to support multiple domain users? We want to integrate SVN with JIRA, and SVN can support multiple domains and we all use LDAP for authentication. Now what shall we do with JIRA? Thanks Jirong

            This would be a very useful function for us. We have multiple businesses in our group, most of the time they require segmented access (and ideally branding) for their spaces, however there are frequently jobs where cross-business collaboration happens, so a single instance for all users is what makes sense, however to continue making everyone feel special and unique, their own domain/branding/templates etc is needed, so +1 from us on this one.

            Craig Castle-Mead added a comment - This would be a very useful function for us. We have multiple businesses in our group, most of the time they require segmented access (and ideally branding) for their spaces, however there are frequently jobs where cross-business collaboration happens, so a single instance for all users is what makes sense, however to continue making everyone feel special and unique, their own domain/branding/templates etc is needed, so +1 from us on this one.

            Hi Tin,

            Honestly, I can't see us adding this as a feature in the near term. What you describe essentially sounds like them wanting totally separate instances but from the one install?

            For a number of reasons that seems like all the downsides of a single install with regards to hosting location, outage impacts etc, with none of the benefits if it's all supposed to be totally separate so you can't cross collaborate etc.

            Perhaps I've missed something specific though and am quite interested in your usecase so if you want to discuss what it is you're trying to achieve some more feel free to email me: jmasson at atlassian dot com.

            Thanks,
            John

            John Masson added a comment - Hi Tin, Honestly, I can't see us adding this as a feature in the near term. What you describe essentially sounds like them wanting totally separate instances but from the one install? For a number of reasons that seems like all the downsides of a single install with regards to hosting location, outage impacts etc, with none of the benefits if it's all supposed to be totally separate so you can't cross collaborate etc. Perhaps I've missed something specific though and am quite interested in your usecase so if you want to discuss what it is you're trying to achieve some more feel free to email me: jmasson at atlassian dot com. Thanks, John

              jmasson@atlassian.com John Masson
              e5839ced1e43 Tin Pham
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: