Merge lp:~deryck/launchpad/reauth-gpg-363916 into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Deryck Hodge on 2012-08-20 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 15843 |
| Proposed branch: | lp:~deryck/launchpad/reauth-gpg-363916 |
| Merge into: | lp:launchpad |
| Diff against target: |
132 lines (+38/-10) 4 files modified
lib/lp/registry/browser/person.py (+4/-0) lib/lp/registry/browser/tests/test_gpgkey.py (+21/-1) lib/lp/registry/stories/gpg-coc/xx-gpg-coc.txt (+8/-8) lib/lp/registry/stories/person/xx-person-editgpgkeys-invalid-key.txt (+5/-1) |
| To merge this branch: | bzr merge lp:~deryck/launchpad/reauth-gpg-363916 |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Benji York (community) | code | 2012-08-20 | Approve on 2012-08-20 |
|
Review via email:
|
|||
Commit Message
Requrie a fresh login from users editing their gpg keys.
Description of the Change
= Summary =
This branch is the final in a series of branches to fix bug 363916. This will ensure that all authentication info for users cannot be edited with an old session. The user will need to refresh his or her login to edit gpg keys after this lands. The work that has gone before added this fresh login requirement for email and ssh keys.
== Proposed fix ==
The fix is pretty simple -- just use require_fresh_login -- which was added in earlier branches.
== Pre-implementation notes ==
I didn't discuss this particular branch with anyone, but I had several conversations with flacoste about the earlier work and branches.
== LOC Rationale ==
I've got LOC credit from earlier work to refactor doctests. This is the final branch to add code, and I believe I'll be -50 lines all told once this lands.
== Implementation details ==
* Add a test to ensure the view redirects if the login is stale
* Add an initialize method which calls require_fresh_login
== Tests ==
./bin/test -cvvt test_edit_
(There will be a few doctests that break, I expect, but I'm running this through ec2 while I get it reviewed. I'll fix up any tests that I find and do another ec2 run to land it.)
== Demo and Q/A ==
* Login to Launchpad
* Get coffee to wait 2 minutes
* Visit a user's profile page
* Click the edit icon next to OpenPGP Keys
At this point, you should be redirect to the login server.
= Launchpad lint =
Checking for conflicts and issues in changed files.
Linting changed files:
lib/lp/
lib/lp/

Looks good.