If you want to allow both anonymous AND authenticated users into a trac
- ie you want to preserve their user name when authenticated, then you
need the Require valid-user anyway, but to allow anonymous in then you add:
Satisfy any
In your situation, you'd only add the Satisfy any to the trac that wants
to allow anonymous hosts in (note that your /login for that trac needs
to be Satisfy all
hth
Tim
Viren Shah wrote:
Hi,
I currently have multiple projects using multiple Trac instances --
all through LDAP. I'm basically doing a blanket auth at the top-level:
<Location /projects>
SetHandler mod_python
# PythonHandler trac.ModPythonHandler
PythonHandler trac.web.modpython_frontend
PythonOption TracEnvParentDir "/data/tracroot"
AuthType Basic
# AuthName "testproject"
AuthName "Trac Project Sites"
AuthLDAPURL ldap://localhost/dc=virtc,dc=com
Require valid-user
</Location>
Now, one of the projects has a requirements to let a couple of
unauthenticated people create tickets and view their Trac site.
Any ideas as to how I could manage that? The current LDAP database that
it authenticates against contains only employees. I could go to using
auth on a per trac site basis like:
<Location "/projects/testrepos/login">
AuthType Basic
AuthName "testproject"
AuthLDAPURL ldap://localhost/dc=virtc,dc=com
Require valid-user
</Location>
<Location "/projects/testproject2/login">
AuthType Basic
AuthName "testproject2"
AuthLDAPURL ldap://localhost/dc=virtc,dc=com
Require valid-user
</Location>
but that would be a pain since I have over 2 dozen Trac projects and
getting more everyday.
Thanks
Viren
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
