implement check_immediate for openid requests
Bug #449708 reported by
Stuart Metcalfe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical SSO provider |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
The current identity provider returns a negative response for all check_immediate requests, requiring a full check_setup request. By implementing check_immediate we potentially make lightweight sso login with ajax easier. Perhaps this should only be available for whitelisted/sso sites?
Testcase ISD_207
Related branches
lp://staging/~canonical-isd-hackers/canonical-identity-provider/bug_449708_check_immediate
- Ricardo Kirkner (community): Approve
-
Diff: 213 lines (+93/-16)5 files modifieddoctests/stories/openid/basics.txt (+31/-0)
identityprovider/templates/consumer/index.html (+6/-0)
identityprovider/tests/test_views_consumer.py (+32/-11)
identityprovider/views/consumer.py (+10/-2)
identityprovider/views/server.py (+14/-3)
visibility: | public → private |
visibility: | private → public |
tags: | added: sp-15 |
tags: | added: marketo-integration |
tags: |
added: 15sp removed: sp-15 |
tags: |
added: sp-15 removed: 15sp |
Changed in canonical-identity-provider: | |
assignee: | nobody → David Owen (dsowen) |
status: | Triaged → In Progress |
Changed in canonical-identity-provider: | |
status: | In Progress → Fix Committed |
Changed in canonical-isd-qa: | |
status: | Confirmed → Fix Committed |
Changed in canonical-isd-qa: | |
status: | Fix Committed → Fix Released |
Changed in canonical-isd-qa: | |
milestone: | none → canonical-identity-provider+2.7.0 |
description: | updated |
Changed in canonical-identity-provider: | |
status: | Fix Committed → Fix Released |
Changed in canonical-identity-provider: | |
assignee: | David Owen (dsowen) → nobody |
assignee: | nobody → Pyae Lin Aung (pyaelinaung2014) |
Changed in canonical-identity-provider: | |
assignee: | Pyae Lin Aung (pyaelinaung2014) → nobody |
To post a comment you must log in.
This has been prototyped successfully for another project. We need to define how it's controlled (eg: whitelisted sites only, user-controlled) but tentatively assigning to the 2.7.0 release.