You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <br...@users.sf.net> on 2014/03/07 20:08:47 UTC

[allura:tickets] #6701 Integrate allura authorization with Git/SVN(over HTTP)

- **Size**:  --> 4
- **Milestone**: limbo --> forge-mar-21



---

** [tickets:#6701] Integrate allura authorization with Git/SVN(over HTTP)**

**Status:** code-review
**Milestone:** forge-mar-21
**Created:** Sat Sep 21, 2013 10:09 PM UTC by Rui Ferreira
**Last Updated:** Thu Dec 05, 2013 04:01 PM UTC
**Owner:** nobody

Right now allura can set permissions for access to code repositories, but they are only applied when cloning repositories over ssh (because of fuse/accessfs). It would be nice if the same was also possible when Git/SVN are accessed over HTTP.

In our deployment we run Git(git-http-backend) SVN(Apache mod_svn), and we created an access handler for apache to handle Git and SVN requests, authenticating against LDAP, and checking permissions against the /repo_permissions/ web service.

I'm attaching the access handler script, with a Git config example inside. The SVN settings should be similar. 

A few missing pieces:
- Unlike accessfs.py there is no caching yet
- Unfortunately I know nothing about Mercurial over HTTP so I never added support for it :S

Hopefully this is useful to someone out there




---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.