On Mon, Feb 16, 2009 at 2:30 PM, Noah Kantrowitz <[email protected]> wrote: > > > On Feb 16, 2009, at 10:59 AM, Ed - 0x1b, Inc. wrote: > >> >> On Wed, Feb 11, 2009 at 1:12 AM, Noah Kantrowitz >> <[email protected]> wrote: >>> >>> On Feb 5, 2009, at 4:36 AM, nik gaffney wrote: >>> >>>> >>>> Hi, >>>> >>>> I am trying to setup trac to be able to register new users and grant >>>> rw >>>> access to an svn repo. It looks like using LDAP would be the most >>>> obvious as both trac and svn can authenticate against a local >>>> server. >>>> With my currentl setup trac can view the svn repo and authenticate >>>> users >>>> with LDAPStore. However, the 'register' link doesn't appear when >>>> password_store is LDAPStore but works ok when using SessionStore. >>>> >>>> As it appears there are several plugins to use LDAP authentication >>>> with >>>> the Acount Manager plugin, I have tried 'TracLDAPAuth' and >>>> 'LdapAuthStore' and couldn't get either to work with the >>>> registration >>>> interface. >>>> >>>> Has anyone managed to get this kind of setup to work, or should i be >>>> trying a differnt approach? >>> >>> The LDAP auth plugin doesn't support modification, nor do I plan to >>> add that. The general use case for LDAP is hooking in to an existing, >>> large company infrastructure. In this case you would already have a >>> procedure and tools for adding/modifying accounts. I don't think it >>> makes sense to try to build these tools into Trac when the whole >>> point >>> is to allow you to use your existing ones. >>> >>> --Noah >>> >> >> -1 >> Noah, please consider other use cases, >> I'm trying to create a system that can do what the OP requested >> without the overhead you're assuming because, in my case, the >> participants span several organizations with incompatible >> infrastructures. The result is that I would very much like to grant >> SVN access based on those that create Trac ID creds. LDAP Auth is >> looking to be the best(only?) bridge between the two. > > The actual problem is that you assume the only usable option is LDAP, > when it is in fact not. It is very common to use htpasswd or htdigest > auth for both Trac and SVN, and if you point them at the same the file > then registrations work across both. This is why making assumptions > is bad :-) > > --Noah >
yes, but how does Trac populate the htpasswd/htdigest files? I've always know them to be essentially static lists and Trac registrations are kept in the database backend..right? The features I am looking for are 1)Trac as the front door, 2) speed of user acquisition with a "self-serve" level of automation, 3) filtering of obvious nonsense, and 4) a degree of uniqueness across users' ID (dupe checking). Additional contact information (email) is nice but not necessary and the IDs created are only meant to be used within the Trac/SVN site with a limited TTL. I should have said "dynamic bridge" between the two, or something - the impression that the list of credentials already existed was incorrect. Ideally (4me) Trac would produce creds that SVN could consume - maybe as a part of a RESTful interface. :) Ed --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
