On Friday, January 22, 2016 at 4:13:03 AM UTC-8, deadf00d wrote: > > Hi Ryan, > > thanks again for the quick reply. > > I think, the 'proxy_pass_header Authorization' directive is only necessary, > when trac should handle authentication. Cf. > https://en.wikipedia.org/wiki/Basic_access_authentication#Client_side > In my setting, I want nginx to handle (not pass) this authorization header. > > Just to be sure, I tried with 'proxy_pass_header Authorization' as well, > but this does not change anything. > > Is there some place, where I can patch the ''environ['REMOTE_USER'] = > environ['HTTP_REMOTE_USER']" line? > I'm new to python, so any directions would speed up my attempts. > > I'm happy to help setting up some useful description for Trac with nginx, > once this works out. > Not that I'm an nginx expert. Using it for a couple of month now... > > Kind regards, > Alex >
I read through the following ticket again: http://trac.edgewall.org/ticket/9206 The following modification might solve the issue: def authenticate(self, req): if self.obey_remote_user_header and req.get_header('Remote-User'): remote_user = req.get_header('Remote-User') req.environ['REMOTE_USER'] = remote_user return remote_user return None -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
