Note: This may be related to python-social-auth/social-app-django#272.
[question]: Is there any assumptions being made about there not being an active user session at the start of the pipeline? If not, where does the default pipeline code make corrections if the active user session is for a different user than the user that is currently logging in?
I'm seeing bugs where the already logged in user is being left in place after the pipeline, and is getting updated with details from a different user that is trying to log in, and I'm trying to determine if we introduced bugs due to a bad assumption.
Thank you.