#python-social-auth

it seems like the query parameters are lost somewhere along the way during /login/twitter, and i have no way to submit the "remember" query param to make the flask backend remember me

neferty: SOCIAL_AUTH_FIELDS_STORED_IN_SESSION = ['remember']

then you can do: session.get('remember')

well, that's done by PSA internally, when it calls to flask_login's login_user, but yeah, that should do the trick, let me try

the problem with parameters is that the majority of providers will validate the redirect_uri and fail if it's not the same configured on their settings

so parameters must be removed and cannot be passed, only solution was to store them in the session

doesn't seem to help since it's still not read back :\

none of those are true, if eg. i do /login/twitter?remember=1 or something

neferty, you are right, it's not taking into account that the value might be in the session

neferty: https://github.com/omab/python-social-auth/blob...

cadillac_: i upgraded to that git commit, and that call (backend.strategy.session_get('remember')) still returns None if i do /login/twitter?remember=1 :\ i'll need to investigate what's in there

oh and i have SOCIAL_AUTH_FIELDS_STORED_IN_SESSION = ['remember'] too

>>> session.keys()

dict_keys(['twitter_state', '_id', 'twitterunauthorized_token_name'])

neferty: I'm debugging it, same happens here, I see the value being stored in the session but once the browser returns from the provider, it's gone

cadillac_: alright. i'm patiently awaiting. for the time being, i'm setting the cookie expire time at the start of every request as a bandaid solution

neferty, the problem is that flask_login uses "remember" name too and it pops the value from the session

so, basically, remember clashes with flask_login internal implementation, changing the name to something else, like "remember_me" does the trick

neferty: fixed https://github.com/omab/python-social-auth/comm...