> As far as I get tell, the only understanding Trac has in terms of users is for > authorization to various functions. That is, there is no list of user to > which you can assign a ticket. As a result, one could assign the ticket to > Anyone, even people who do not have access to the system.
Not really. Trac manages "permissions" - who can do what, and the web server manages "authentication" - verify that the user is allowed to access the server, and provide the username to Trac If you activate the "restrict_owner" option (see the TracFaq for ex.), nobody can assign a ticket to a non-existing user, as the "assign to" free text field is replaced w/ a drop-down list filled w/ exising usernames. > That is, the only users Trac knows about are the ones Apache > knows about. Is that correct? Not fully. Apache does not actually "know" the users: it passes the credentials (user / password) to an authentication backend. Apache forwards the credentials, and authorizes or rejects the user based on the response of the backend. If you use a LDAP backend for example, you can add or remove users to the LDAP directory without changing anything to the Apache configuration. > Is there *currently* any other user administration functions? What > is planned? There are some great plugins available: AccountManager for example, that replaces the HTTP authentication with a custom authentication scheme and manages the accounts: http://trac-hacks.org/wiki/AccountManagerPlugin and the WebAdmin plugin (which will be part of the Trac core in the next major release) allows to manage the Trac permissions from the web interface. Cheers, Manu --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
