Stephen A. Cochran Lists wrote: > > On Feb 1, 2006, at 4:49 PM, Brad Anderson wrote: > >> I also have a Trac plugin that will do this. It's in kinda rough >> shape, but >> works for me. I enable this plugin, and disable the default Trac >> auth plugin, >> and I'm all set. It has a login page, cookies, and if you use my >> UserDirectory patch, you can restrict users (ticket owners, etc) to >> only the >> users in your db table. > > > > Does it work for multiple projects? Having a way to make permissions > either specific to a project or global for all projects would be useful. >
yes, the tables have an envname field, for which Trac env the users belong, and the plugin is aware of the 'all' envname that is global for all projects. In the tables, I assign the users to an env or to 'all' and also to groups. Then, in each project, I give the groups permissions. There's a tarball of the plugin somewhere in the list, but there have been changes since then. Karol Krizka got it working as well, but for SQLite. There's work to be done on it to use a DatabaseManager for a central db connection. It'd be great if Trac could be modified to be more flexible on this front, but since they have one db per project, it's unlikely. I also have a nasty connection leak somewhere. I'm not sure if it's in my code or in Trac with Postgres in general. Interested in helping? BA _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
