Cannot login with social account anymore after migration from DSA (but association is OK)

[Karmak23]

Hello,

I recently migrated 1flow from DSA to PSA, following the official doc and this one as a complement.

I cleared all sessions.

After that, I'm unable to signin with any social account (tested twitter & googleo2). I'm always redirected to the LOGIN_ERROR url, but there is no message, no exception, nothing.

What is strange is that associating social accounts to a local one works perfectly, so API keys & secrets name change typos seem to be out of cause.

What I tried :

• using PSA latest from PyPI, and @master from github.
• removing all my pipeline functions. This lead me to fix portability bugs (backend classes name changes…), but even with only the default pipeline left untouched, I still cannot signin.

Settings files:

• Django auth backends are in the middle of common settings.
• PSA settings.
• API keys are fetched from the environment as suggested by 12factor.

The only thing I did not set is SOCIAL_AUTH_URL_NAMESPACE = 'social' because I don't know if I need a custom namespace or not; I guessed not, because association/disconnect works as is.

I've started to print() everything at diverse locations of PSA's do_complete() and other functions, without any relevant result. I've even re-implemented a debug() pipeline fuction, but the pipeline isn't entered at all (the function is not called, do_complete() returns no user before).

Any hint on what I could search / change / do to find where the issue comes from ?
My hint is that everything worked fine with DSA ;-)

PS: I use Django 1.6. we had mongodb in the past but DSA tables were stored in PostgreSQL; now i've nearly switched all back to PG only, so there should be nothing special about PSA on this side.

thanks & best regards,

[Karmak23]

Ping please ?
Every time I associate an account, it works, but user.social_auth.get().tokens is None.

[Karmak23]

Hi,
I would have expected some hints to help me find what could have been wrong, but nevermind.

I finally solved my problem. For future readers, here is what was wrong :

• some settings coming from DSA should be WIPED OUT. Here, SOCIAL_AUTH_EXTRA_DATA=True was making PSA pipeline crash, without any exception.
  • After a search I see now it's listed in deprecated bits, but I never got any deprecation warning in DSA about it in 2 years. PSA picks it up with a totally different meaning: it's now a valid setting again, but should not contain the same type of settings. There was a ValueError raised here, but silenced at some point.
  • Setting SOCIAL_AUTH_RAISE_EXCEPTIONS=True was not of any help, even with DEBUG=True, even with SocialAuthExceptionMiddleware enabled, the exception was still silent. I was only redirected to LOGIN_ERROR_URL, not even without a message. I needed to log and try/except all pipeline functions one by one to find where the problem was. I think the pipeline debugging should be made easier to enable (like requests-oauthlib does, with some logging.debug() call here and there).
• pipeline arguments order changed from DSA to PSA. I successfully tackled the social_auth → backend argument rename and some other obvious bits, but not the arguments order changes, which are not stated in the migration documentation. I finished by using only **kwargs in my pipeline functions, getting only the arguments I needed at every function beginning.

Hope this helps someone else migrating from DSA to PSA.

@omab , I can provide a PR for a debuggable pipeline, I've got a partially (but cleanly, with python logging, namespace, etc) patched PSA ;-)

regards,