omab/django-social-auth — Issue #163: Twice linked external accounts
Author: colemickens
Created: 2011-10-22 23:08:21+00:00
State: open

At example site:

1. Login via Facebook.
2. Log out
3. Login via Twitter
4. "Link Additional Account": Facebook.
5. Server explodes with 500 Error.

Is this not possible to handle the way django-social-auth is currently written or is it simply not caught at the example site?

Futher, is there a "correct" way to handle these sorts of cases as open openid/oauth "best practices" or something?