Merge lp://staging/~vorlon/summit/oauth2-support into lp://staging/summit
Status: | Needs review |
---|---|
Proposed branch: | lp://staging/~vorlon/summit/oauth2-support |
Merge into: | lp://staging/summit |
Diff against target: |
197 lines (+95/-2) 9 files modified
requirements.txt (+1/-0) summit/common/context_processors.py (+4/-0) summit/common/templates/base.html (+1/-1) summit/common/templates/done.html (+10/-0) summit/common/templates/login.html (+13/-0) summit/schedule/templates/schedule/actions.html (+1/-1) summit/settings.py (+5/-0) summit/social-backends/debian.py (+55/-0) summit/urls.py (+5/-0) |
To merge this branch: | bzr merge lp://staging/~vorlon/summit/oauth2-support |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Summit Hackers | Pending | ||
Review via email: mp+215534@code.staging.launchpad.net |
Description of the change
Preliminary support for oauth2. This pulls in a new django module dependency, and also only works if you also register and add in oauth2 keys, which you need to get from your oauth2 provider.
Unmerged revisions
- 226. By Steve Langasek
-
Replace another reference to /openid/login with login_url
- 225. By Steve Langasek
-
Initial support for Debian SSO
- 224. By Steve Langasek
-
Simplify the oauth2 support
we don't actually need separate url handlers, we can just include the
upstream ones and set LOGIN_URL to whichever provider we want (e.g.,
/login/google- oauth2) in our individual django app. If someone really
wants to have multiple auth providers from the same app, they can figure
that out on their own, but currently it doesn't look like an interesting use
case. - 223. By Steve Langasek
-
Make the 'login' link on the navbar configurable via LOGIN_URL in settings.
- 222. By Steve Langasek
-
Initial support for oauth2 (using the Google backend for testing)