Re: Review Board and remote user middleware/backend - user not forced to enter first/last names and email address

Doesnt the firstname, lastname and email set the values only on auth_user table? If its only setting it locally in the reviewboard database, wouldnt it be possible to include those variables even if the auth_backend is not builtin? The current preferences screen shows those 3 variables only if

Re: Review Board and remote user middleware/backend - user not forced to enter first/last names and email address

I have a custom middleware: http://python.pastebin.com/wAcCNsTE I blank out the names and email address but this doesn't help. Is there something else I should be doing in my middleware? Thanks On Feb 22, 3:20 pm, Stephen Gallagher step...@gallagherhome.com wrote: On 02/22/2010 03:10 PM,

Re: Review Board and remote user middleware/backend - user not forced to enter first/last names and email address

Ah - I think it's because I was still using the RemoteUserBackend. I disabled that and it seems to work ok. On Feb 23, 9:48 am, Stodge sto...@gmail.com wrote: I have a custom middleware: http://python.pastebin.com/wAcCNsTE I blank out the names and email address but this doesn't help. Is

Re: Review Board and remote user middleware/backend - user not forced to enter first/last names and email address

Actually, it's probably okay to have it there for all backends. Ideally, we would stay in sync with the remote server (for LDAP, NIS and Active Directory) but we don't do that today. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. -

Review Board and remote user middleware/backend - user not forced to enter first/last names and email address

I'm using the remote user middleware/backend to support basic http authentication: 'django.contrib.auth.middleware.RemoteUserMiddleware', and it seems to work nicely with Review Board. Apache forces a user to login and then this middleware/backend automatically creates the user in Django. The

Re: Review Board and remote user middleware/backend - user not forced to enter first/last names and email address

On 02/22/2010 03:10 PM, Stodge wrote: I'm using the remote user middleware/backend to support basic http authentication: 'django.contrib.auth.middleware.RemoteUserMiddleware', and it seems to work nicely with Review Board. Apache forces a user to login and then this middleware/backend

Re: Review Board and remote user middleware/backend - user not forced to enter first/last names and email address

Thanks. So I would need to write a custom backend/middleware instead? On Feb 22, 3:20 pm, Stephen Gallagher step...@gallagherhome.com wrote: On 02/22/2010 03:10 PM, Stodge wrote: I'm using the remote user middleware/backend to support basic http authentication:

Re: Review Board and remote user middleware/backend - user not forced to enter first/last names and email address

Or we should figure out a scheme to allow for setting that on other backends. Could check an attribute on the backend. Maybe assume that we can set that info and have a flag for turning it off, which LDAP, NIS, etc. can do. Christian -- Christian Hammond - chip...@chipx86.com Review Board -