patchmetrics login fails with camelcase emails

[Deepti B. Kalakeri]

When a user with a camelcase lp id tries to login to patches.linaro.org fails with the

 "Integrity Error, duplicate key voilates unique key constraint patchwork_person_email_key "

The error occurs because for now, auth_user table stores the email address as provided stored in the launchpad details of the user, but the same email information is stored in lowercase in the patchwork_person table.

So, whenever such a camecase email id user tries to login next time, it appears that there is no matching email records in the person table and hence tries to create a new user in auth_user and patchwork_person table and fails with integrity error.

A more detailed information on the problem and the workaround used to solve it can be found in bug
 https://bugs.launchpad.net/linaro-patchmetrics/+bug/1046911.

The bug here is a record that we need to modify the patchworks code to have a permanent solution.
Here are the changes we need to make to the patchwork code.

1) Store similar case email information into auth_user and patchwork_person. Since the information in pacthwork_person is stored in lowercase, change the auth_user to save in the same case.
2) Plus, change the configuration option for django-openid-auth, to avoid user details updated from OpenID Simple Registration or Attribute Exchange extension data each time they log in, add the OPENID_UPDATE_DETAILS_FROM_SREG = False.
   Information on OPENID_UPDATE_DETAILS_FROM_SREG is at http://bazaar.launchpad.net/~django-openid-auth/django-openid-auth/trunk/view/head:/README.txt

[Milo Casagrande (milo)]

Due to the age of this issue, we are acknowledging that this issue will likely not be fixed, is no longer applicable, or was already fixed by an indirect change. If this issue is still important, please add details and reopen the issue using http://bugs.linaro.org.