On Tue, Feb 17, 2009 at 9:43 AM, Jeff Hammel <[email protected]> wrote: > On Mon, Feb 16, 2009 at 01:30:03PM -0800, Noah Kantrowitz 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: >> >> >> >> 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. >> > >> > -1 >> > Noah, please consider other use cases, >> >> The actual problem is that you assume the only usable option is LDAP, >> when it is in fact not. > > +1 on this. While auth is complex in trac, I'd rather have configurability > and malleability than tailoring towards perceived common use cases. >
The only thing I want to add to this thread is that if devs are finally convinced of supporting 'write' operations in LDAP dirs, pls, provide separate components for each scenario ... I mean «Default_LDAP_XXX» for read-only ops ... and «Full_LDAP_XXX» for read/write ops (possibly connected through inheritance or maybe not ...). Read-only access to LDAP dirs is mandatory most of the times I have set up Trac ... so this would be very useful to avoid conflicts in organizations (and sometimes chaos ;) ... IMO ... PD: ... users are always right ... :) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
