Uses authenticated access to Launchpad when anonymous will do
Bug #906846 reported by
Jonathan Lange
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Distributed Development |
New
|
Undecided
|
Unassigned |
Bug Description
Much of what lp:udd does with Launchpad is read-only: add-import-jobs, list-packages etc. All of this could be done using anonymous Launchpad access. The only things that need write access to lp over the API are delete-
Using read-only access when only read-only access is needed prevents accidental or malicious writes, and simplifies configuration for deployments that don't need write access.
tags: | added: canonical-webops-ca |
To post a comment you must log in.
It would also make it harder to tell that it is udd doing things,
which is quite nice for us. Please consider at a minimum setting a
custom user agent if you start using anonymous access. However,
ideally, I'd say keep using authenticated access.