Two confluence URL's for one instance

[Rethabile Morena]

Good day,

We would like to find the best solution to hosting two different departments under one confluence instance - and ensure that the permissions are restricted per department (one should not be able to access the other department's content).

We currently have a huge chunk of spaces created, and therefore cant go with the option to create two spaces and have 'sub-department' content as pages. Is there a possibility to have 2 URL's created for 1 instance (meaning a one link will direct a user to his relevant departments confluence view which is layed out with all their spaces)?

Please advise/suggest

Regards

Rethabile M

[Nic Brough [Adaptavist]]

You could set up a different url and have people landing on it be redirected or even rewritten, but they will end up working on the baseurl quite quickly.  Confluence only runs on the baseurl and when it presents links to the users (on screen and in email), it can only use that base url.  There's no way it can possibly know that you've got another url for it.  So they will quickly click on something that takes them back to links runnin gon the base url for it.

[Renato Rudnicki]

Hi Rethabile, 

I believe for this environment, a good solution would be you setup a reverse proxy. Keep in mind, Atlassian doesn't provide support to reverse proxy but this doesn't mean it won't work. 

Another possibility would be have two instances of Confluence. One for each space. In my personal opinion, if you have a huge environment, may be a good idea you have more than one Confluence running. To don't need to recreate the use permissions and groups for each Confluence twice, you could have this users in a LDAP or Crowd base.

Regards, 

Renato Rudnicki

[Nic Brough [Adaptavist]]

A reverse proxy is something a lot of Atlassian sites do - running behind a web-server. It does NOT solve the problem that when you access Confluence over the second url, internally, it still links back to the base url