forwardCheckAuthenticated doesn't check existence if a permission is not specified

Bug #766955 reported by William Grant
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Henning Eggers

Bug Description

forwardCheckAuthenticated doesn't behave correctly when its permission argument is None. It correctly defaults to self.permission, but assumes that it doesn't have to check_permission_is_registered. This isn't correct: the object is probably of a different type, so the check must be performed or the adapter lookup may fail.

Related branches

Revision history for this message
Henning Eggers (henninge) wrote :

It should also return False if no such adapter exists, just like checkPermission in LaunchpadSecurityPolicy.

Changed in launchpad:
assignee: nobody → Henning Eggers (henninge)
Changed in launchpad:
status: Triaged → In Progress
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
Changed in launchpad:
milestone: none → 11.05
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :

Fixed in stable r12943 (http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/12943) by a commit, but not testable.

tags: added: qa-untestable
Changed in launchpad:
status: In Progress → Fix Committed
Brad Crittenden (bac)
Changed in launchpad:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.