On Wed, Feb 18, 2009 at 2:07 PM, Erik Bray <[email protected]> wrote: > > On Tue, Feb 17, 2009 at 9:43 AM, Jeff Hammel <[email protected]> wrote: >> +1 on this. While auth is complex in trac, I'd rather have configurability >> and malleability than tailoring towards perceived common use cases. >> >> Jeff > > Though I still argue that the AccountManager plugin,
+1 for its inclusion in Trac ... at the end everybody installs AccMngrPlgin ... AFAICS in this list ... and since there is no way (... so far ;) to log users out off the site without using AccMngrPlgin ... I think this is ok ... just like WebAdmin is ok in Trac 0.11.x ... ;) > or at least parts > of it (including form-based login and user registration) should come > with Trac +1 > and should be the default configuration. > +0.5 ... this depends on «strategic decisions» ... - default to form based auth if you want to ease the task to specific users not familiar with HTTP auth mechanisms ... - default to HTTP auth if you want to be consistent with standards (... are there stds for form-based auth ? ...) and RFCs ... and be backwards compatible, and allow seamless integration with of other services built on top of Trac (e.g. XML-RPC ;) ... IMO (... CMIIW ;) Trac is mainly used by developpers interested in managing their own projects, build their own management infraestructure and services on the PMS (excelent :) architecture, and make it be part of a more complex environment deployed in organizations, by automating PM tasks and more ... At least for me, now, HTTP Auth (... sometimes NTLM is requested first, but this is only 10% of the whole ...) is *EXPLICITLY* a *MUST* in every Trac instance I have installed so far ... that's what users request ... most of the time (... my experience ... ;). > Most users seem to want to be able to just install Trac and have it > handle user registration, +0.5 ... except when using central dirs (e.g. LDAP ...) so that many apps may share data ... in this scenarios I have quite often found domain admins which dont want anybody writing data in the dir they are responsibles for ... > > It always seems like 90% of the support questions on trac-users are > related to setting up authentication and user management. ... it seems so ... yes ... > Now of > course there are lots of users who have more advanced use cases, but > there's no reason Trac wouldn't be able to maintain its existing > flexibility for those cases. ... without jeopardizing important tasks within organizations ... like LDAP admin/write ops. Sometimes LDAP stores centralized information very important to enterprises and many other apps and services depend on this info ... Modifying data in LDAP could be a source of chaos ... That's why everybody says in advance : «Are you going to write anything in MSAD?» (i.e. LDAP ;) and I have to tell them «Nop ... take a look at the code here. There is no way for Trac to modify data stored in MSAD». Believe me, such arguments are often important. All this is IMO ... ;) PD: ... sorry if part of this is OT ... -- 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 -~----------~----~----~----~------~----~------~--~---
