Merge lp:~lfaraone/django-openid-auth/custom_response into lp:~django-openid-auth/django-openid-auth/trunk
Proposed by
Luke Faraone
Status: | Needs review |
---|---|
Proposed branch: | lp:~lfaraone/django-openid-auth/custom_response |
Merge into: | lp:~django-openid-auth/django-openid-auth/trunk |
Diff against target: |
69 lines (+10/-5) 2 files modified
django_openid_auth/tests/test_views.py (+3/-0) django_openid_auth/views.py (+7/-5) |
To merge this branch: | bzr merge lp:~lfaraone/django-openid-auth/custom_response |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
django-openid-auth developers | Pending | ||
Review via email: mp+195845@code.launchpad.net |
Description of the change
This branch allows you to specify a custom render failure handler.
This is used in one deployment to redirect users to a registration form when they authenticate without already first having an account on our system.
To post a comment you must log in.
Unmerged revisions
- 108. By Luke Faraone <email address hidden>
-
Add an openid_response parameter to default_
render_ failure This allows the failure handler to take actions depending on the contents of
the failure.For example, we might want to handle "Unknown user" specially and maybe create
an account for the user.