incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cory Johns" <>
Subject [allura:tickets] #6701 Integrate allura authorization with Git/SVN(over HTTP)
Date Wed, 19 Mar 2014 22:13:27 GMT

I refactored the handler and converted it to POST to a (configurable) login URL for auth (e.g.,
`/auth/do_login`).  The idea being that it use Allura to verify the auth, so that whatever
auth method Allura is configured to use gets used automatically by the SCM.


** [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:** Tue Mar 18, 2014 03:00 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 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 because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message