History | View | Annotate | Download (8.3 kB)
Proper next parameter handling in third party logins
Excluding shibboleth all auth modules require two additional redirectscausing `next` parameter to be absent on the final url.
Auth providers improvements
- Enrich login/logout messages.- Clear unverified accounts when user adds the same third party account to an existing account.- Other minor improvements.
Merge branch 'latest-quota' into feature-astakos-tables
Conflicts: snf-astakos-app/astakos/im/models.py snf-astakos-app/astakos/im/views.py
Configurable login method one per user limit
Initial use django-tables2
improves table view development by spliting table data access and presentationonto separate layers.
Various auth providers fixes/improvements
- Handle invalid login after auth method add request- Fix auth method add for unauthenticated users- Third party auth providers helper methods in astakos.im.target module- Provider login url template tag that handles code,key,next url params
Show message after login with third party provider
Auth providers fixes
handle is_available_for_{create, add}
Handle invalid google auth response
Force login when adding third party auth providers
use proper oauth parameters to force user to login and confirm his thirdparty account every time he adds a new login method
Google and LinkedIn oauth support