> I actually skipped that part on purpose because it lists a .htaccess > file, and I thought that all the auth info would be in Postgres > rather than a .htaccess file.
I think you missed something here: there are two pieces for authentication: 1/ where the authentication data are stored (.htaccess, Postgres, whatever) 2/ how an user is authenticated against the storage data You can change 1/ with a different backend, but you still need to configure your web server to tell it where to find authentication data and how to use them. You can use a Postgres backend as the authentication storage if you want, but that does not eliminate the need to define the appropriate rules in the web server configuration. BTW, Trac does not handle authentication at all (it's the web server role), only permissions. It is therefore agnostic about the authentication storage backend. I strongly advise your first use .htaccess to configure the authentication rules, then once it work, move to a Postgres backend in a second phase. HTH Manu _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
