associate user with social identity based on email address

We have a number of existing accounts in the legacy IAR database which only have an email address to uniquely identify them. Make use of Python Social Auth's ability to associate users by verified email to "grandfather in" existing users.

Once merged, put #16 (closed) back to ~"workflow::sprint ready".

changed milestone to %Sprint 93

mentioned in issue #16 (closed)

changed the description

changed milestone to %Sprint 94

changed milestone to %Sprint 95

@rjw57 is this necessary to redeploy production with this?

Ah, yes, otherwise people who sign in will end up with new user accounts.

But we don't have any special users so it doesn't really matter.

It's worth merging anyway though.

what's the best way of testing it?

signing into one of the instances and making sure you're amc203 and not some randomly generated user. If there's already an "amc203+random junk" user, deleting it and trying to sign in again.

(after having restored the backup first)

Or, thinking about it, you could create an amc203 user with email address amc203@cam.ac.uk via ./manage_development.sh shell before signing in for the first time. If you end up signing in as that user and not having a new one created, it's working.

approved this merge request

changed milestone to %Sprint 96

@nb745 it would be good to review any old MRs like this as part of handovers and get them closed or associated with an up-to-date issue if still wanted.

@rjw57 This change is still relevant, do you know whether it should be merged, 4 years later?

I infer it's non-essential given the timeframe (!) but good to either merge or close.

Honestly, I have no idea at this point. At first glance, the config change doesn't seem to have survived through to the relevant section of the boilerplate and so the rest of our apps seem to survive without it .

left review comments

closed

changed the description