Hi, 2011/5/26 Graham Dumpleton <[email protected]>: > What is the reason that you need to change req.user in the first place? we are using the auth handler on different servers in different locations. Use case:
Bob works at Office1. When he is at Office1 he just enters "bob" as a username - the domain "@office1.example.org" is being appended by the Python auth handler. When Bob is at Office2 he'd need to use "[email protected]" as his username; otherwise "[email protected]" would be assumed (and bob@office2 is very likely a different user than bob@office1). We are using multiple authentication mechanisms for the different offices (the Python script knows which kind of authentication should be used for each user domain). I know this is kind of weird - I did not design this thing. The main problem is that I can neither stick with just "bob" as a username (the domain needs to be appended) nor can I ask the users to enter their full username (including the domain) everytime they log on. This is why I need to append the domain automatically in the Python script (the logic for this has worked well for several years). > There is a back door way of doing what you want but it entails needing > to writing a C extension or use some Python SWIG bindings which exist. > I am not sure though whether I will continue to keep the backdoor > though as no one has expressed any real interest in developing the > idea. *sigh*, this does not look like a clean solution. I hope I gave you a proper use case scenario for this kind of setup, maybe you'll consider an official way of modifying the remote user (just like mod_python). Thanks for your efforts. Regards, Frederik -- 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.
