Enable extra htpassword protection to confluence url alone

[nisamudeen97]

Hi,

We have jira and confluence in the same url,  we wanted to enable extra htpassword protection for confluence url alone.  Is it possible? 

[nisamudeen97]

..

[Nic Brough -Adaptavist-]

You can not run Jira and Confluence on the same url, their base urls have to be different.

You can use your proxies password function to put an additional password in front of Confluence, but I strongly recommend that you do not, you should be using the user's accounts to control access.

[nisamudeen97]

Hi,

We are planning to move existing confluence towards a subdomain.   Can you please share documentations for the same.  Currently jira and confluence are working on url service.domain.com

Jura url  service.domain.com

Confluence service.domain.com:8443

We are planning to move confluence to  confluence.domain.com

Is it possible to update our current license to latest confluence and use it in our existing infrastructure?

[Nic Brough -Adaptavist-]

I would do this with a reverse-proxy.  

Working with minimal changes to your names, I would:

• Redirect service.domain.com so that it lands on your.proxy.server.com
• Change Jira so it serves up Jira on service.internal.domain.com/jira
• Change Confluence so it serves up Confluence on service.internal.domain.com:8443/confluence
• Set up the proxy so that it proxies service.domain.com/jira to service.internal.domain.com/jira and service.domain.com/confluence to service.internal.domain.com:8443/confluence

I'd probably also take advantage of this to simplify the setup, going back to serving Jira on the default port of 8080 and Confluence on 8090, and offloading all the SSL on to the proxy.

A proxy would also make it easy to do your htaccess protection (although I still wouldn't bother)

You can upgrade to any version of Confluence that is released before the end of the licence.