I imagine that it would have something to do with setting identity.source to "http_auth", but the docs are vague on this...
see: http://docs.turbogears.org/1.0/Configuration#visit-and-identity-configuration-reference On Dec 18, 2007 2:52 PM, Ted Pollari <[EMAIL PROTECTED]> wrote: > > TG list readers -- > > I'm trying to integrate (my first) TG app into our production > environment, which uses Apache2 to host a number of other web > resources, all of which are protected by basic authentication, done by > Apache2. I'd really like to be able to use the existing > authentication framework but still use identity in TG for fine-grained > permissions, etc. How do I get the basic auth. done by apache2 to > play well with identity in TG? I'd prefer (and am currently using) > mod_wsgi to deploy this TG app. > > I know trac simply takes the REMOTE_USER header passed along by > apache2 when it's deployed via mod_wsgi -- so is there something > similar TG can do? > > If there is, any pointers to examples/how-to's would be great. So > far, my searching has failed me. > > Thanks in advance for any insights/pointers... > > > -ted > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
