summaryrefslogtreecommitdiff
path: root/ansible/trove-setup.yml
diff options
context:
space:
mode:
authorPedro Alvarez <pedro.alvarez@codethink.co.uk>2015-11-09 16:54:30 +0000
committerRichard Ipsum <richard.ipsum@codethink.co.uk>2016-01-26 12:11:35 +0000
commiteca82164d36504fb4dad9b6e0d62eef11d2a4aaf (patch)
treefca1c0baf430c3452c6fc16e9c746b1cbb098bb5 /ansible/trove-setup.yml
parent4c1a02ebe6e5a65b6a1bf79e3320b42f33222f3b (diff)
downloadtrove-setup-eca82164d36504fb4dad9b6e0d62eef11d2a4aaf.tar.gz
lighttpd: Only require HTTPS authentication for Gitano URLs
Previously the whole of git.baserock.org was effectively inaccessible over HTTPS, because it would require a username and password for all HTTPS requests. This was done to ensure that we don't make Trove "insecure by default" by allowing access to hidden repos over anonymous HTTPS. Firstly, we only need to require auth for the actual Gitano URLs. The other ones (cgit, lc-status.html, releases) are identical over HTTP and HTTPS anyway, so there's no point in hiding them on one protocol but not the other. Also, I have now verified that Gitano's CGI scripts authenticate based on the REMOTE_USER variable set by mod_auth, and if this isn't set they treat the request as anonymous and correctly deny any requests that the anonymous user doesn't have permissions for. This is noted in a comment. The behaviour of Gitano-over-HTTPS in Trove should be completely unchanged by this commit, however. Change-Id: Ie5dbc3bd3ab8d37ef3e5c08c9541c571944e1f58
Diffstat (limited to 'ansible/trove-setup.yml')
0 files changed, 0 insertions, 0 deletions