On Feb 1, 2006, at 5:07 PM, Brad Anderson wrote:
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?
Sounds pretty good. I just got trac working with .htaccess file just
to make sure everything was working, but I think I would like to see
what the db plugin could do. Can't promise how much help I would be,
but if I fixed something I'd be sure to kick it back.
I'm in the process of setting up CAS (WebSSO system), so I might look
at using that to do the Apache authentication .
I'm still not clear from this thread where trac stores authorization
info by default. Is it in the project's db (either sqlite or
postgres)? Where does trac-admin put the user permissions for a project?
Steve
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
