Graham, My use case is similar to Frederik's except that I'm using OFFICE1\user and prepending "OFFICE1\" to the user's name when none is provided (no "\" in name). My situation isn't as restrictive as Frederik's, but my fundamental need for manipulating req.user is because the subversion log shows the username exactly as it was entered (office1\USER, OFFICE1\USER, office1\user, etc.) so I normalize the case to ensure that the log looks clean. Since I'm using subversion with Trac, this log history gets synced to the Trac tables so this problem also contaminates our Trac instance. When using Python for Apache authentication it would be nice to support some form of flexibility in influencing the REMOTE_USER value. If it isn't reasonable to support a custom function, perhaps a generic sanitation method that allows for some configuration parameters via the Apache conf. These optional parameters could be a domain delimiter (@, \, etc), prefix/suffix, domain case, and username case. It is unfortunate that we are at the mercy of subversion blindly putting this value in the revision history, but this may be a show-stopper for some people's adoption of mod_wsgi.
Thanks, Brian -- You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en.
