Details
-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
Description
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.
Attachments
Issue Links
- is related to
-
CONFSERVER-19818 Support accessing Confluence from alias that is different to the server base URL
- Gathering Interest
-
CONFSERVER-43178 Confluence behind multiple reverse proxies
- Gathering Interest
- relates to
-
CONFCLOUD-24274 Allow Support for Multiple Domains through Purchasing of Multiple Licenses
- Closed