omab/django-social-auth — Issue #278: Partial pipeline removed from session storage if exited and reopened
Author: Dru89
Created: 2012-03-02 03:55:53+00:00
State: open

Given the following Pipeline:

```python
SOCIAL_AUTH_PIPELINE = (
# ...
'social_auth.backends.pipeline.associate.associate_by_email',
'social_auth.backends.pipeline.misc.save_status_to_session',
'commons.pipeline.redirect_to_username_creation_form',
'social_auth.backends.pipeline.user.get_username',
# ...
)
```

I would expect the session data to be passed to `partial_pipeline` (or whatever `SOCIAL_AUTH_PARTIAL_PIPELINE_KEY` is set to). However, if I ask the user for a username, the session data is passed and I can access it once. If the user then navigates away from the page and then back to the login page, the pipeline data is removed from session storage until the next time the user tries to log in, where the process starts all over again.