Unauthorized on public blueprint which is a dependancy to an embargoed one
Bug #1081773 reported by
Francis J. Lacoste
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
j.c.sackett | ||
Bug Description
Steps to reproduce:
1. Create a public blueprint
2. Create a blueprint on a private project
3. Add the public blueprint as a dependency to the private one.
4. Log out and visit the public blueprint page
You'll get a 401 followed by a 403 error. What I'd like would be to get the public blueprint page with either the private node removed from the dependency graph, or at the very least marked [redacted].
A much less useful alternative would be to prevent me from creating such a link in the first place.
Related branches
lp:~jcsackett/launchpad/blueprint-private-traversal
- Deryck Hodge (community): Approve
-
Diff: 393 lines (+140/-47)8 files modifiedlib/lp/blueprints/browser/specification.py (+7/-4)
lib/lp/blueprints/doc/specgraph.txt (+20/-16)
lib/lp/blueprints/doc/specification.txt (+4/-4)
lib/lp/blueprints/interfaces/specification.py (+12/-4)
lib/lp/blueprints/model/specification.py (+37/-9)
lib/lp/blueprints/model/tests/test_specification.py (+55/-8)
lib/lp/blueprints/vocabularies/specification.py (+2/-1)
lib/lp/blueprints/vocabularies/specificationdependency.py (+3/-1)
| summary: |
- Unauthorized one public blueprint which is a dependancy to an embargoed + Unauthorized on public blueprint which is a dependancy to an embargoed one |
| Changed in launchpad: | |
| assignee: | nobody → j.c.sackett (jcsackett) |
| status: | Triaged → In Progress |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
