#python-social-auth

johtso ping

Hi myusuf3

cadillac_ ping

mitias?

so I have all the tables etc

but the create user pipeline step inconsistently returns wrong values

as you can see user is created.

it just worked fine

now I am going to try it again

i logged out

sign up again which should trigger login

and it failed.

as you can see in the comments in the create_user, the social object isn't always return

myusuf3: I see different emails in the tables

one is esparzaapril@ymail.com and the other one is isobel.price@gmail.com

you are right

i copied wrong row

fixing

fixed

refresh

social object ends up going null

in the cases where it doesn't work.

I see that the user_id column in the social_auth_usersocialauth table is pointing to a different id than the one listed in the other table

again another fault of mine

i can show you in screencapture

it working sometimes

and other not

if you would like.

sure

hnm

made a video and learned something

when the is_new fails it creates a new user and deletes the old one

which is why I was getting inconsistent data for the gist

i recored a video showing you the flow

give me a second

deletes the user in the auth_users table?

yes

and creates a new one with new id

there's nothing in python-social-auth that deletes entries from auth_users table

not my auth_user

your table

in social auth table

how are you "logging out" in your tests?

yes

video incoming

what's the endpoint you call to logout

?

django.contrib.auth.views.logout

@cadillac_

^^

when you do "logout" is anything calling the disconnect api?

also, when you do "logout" is the user social auth entry in the db still present?

checking

it should be

just logged out its precent

wow the record is deleted when I successfully login

remember how I showed you logs in sometimes

when that went through it record gets deleted

looking for through

now

these are the only two pipeline steps in between

standard auth stuff and my custome stuff I previously linked

I dont sse anything that deletes

cadillac_ ^

right, there's nothing that deletes unless you are invoking the "disconnect" code

myusuf3: what happens if you disable your custom pipelines, like removing or renaming the setting to let the default one run

cadillac_ those are needed for traditional auth connects

which ones, I am not seeing where this is happening

do you guys hook into django.contrib.auth.views.logout\

no, we don't

I mean trying to rename `SOCIAL_AUTH_PIPELINE` into `DISABLED_SOCIAL_AUTH_PIPELINE`, let the normal pipeline run and see what's the behavior then

kk trying

give me a second

nothing happen

no login or user creations

nothing in the DB?

is create_user in the default flow?

nothing

yeah, it's the default pipeline https://github.com/omab/python-social-auth/blob...

putting in some breakpioints give me a second

you sure its nothing to do with complete/email post and stuff like that

I have to do default with my user_oassword in there

but its weird why create user isn't creating auth_user right?!

create_user will create the user unless it's identified that the user is already created

and that record would be in the auth_user table?

right

well the sky is red

and nothing works

any ideas here

no ideas here, I suggest an step-by-step debug from the starting point to determine where's the entry getting deleted

hmm but its doing something that you are saying it shouldn't do with default pipeline

right?

the delete?

yeah

how is that even happening?

that escapes my mind, there's nothing in PSA coded to do that

thanks, I will cotninue to look

but if you can think of anything, would be apprecaited.

I'll let you know if something comes to my mind

try enabling the output for the SQL queries getting run, that might point what's triggering that query

i could just turn on sql logs

kk cool

thanks.

thanks for taking the time.

no problem

cadillac_ ping

so it is being deleted on login

i found it.

thanks it was us.