Add Git HTTPS push tokens for snapcraft experiment

Bug #1824399 reported by Colin Watson on 2019-04-11
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Colin Watson

Bug Description

There's some experimental work going on in snapcraft that would be made easier by being able to request temporary push tokens allowing users to push to Launchpad-hosted Git repositories over HTTPS (so that they don't have to set up SSH keys). This is a special case of the more general requirement for what some other sites call "HTTPS access tokens" or similar, but it's simpler because we don't need to make the tokens persistent or add UI for managing/revoking them, but for the moment we can just issue tokens with a relatively short expiry period.

I'm working on this, and am filing this bug to track the work.

Related branches

Colin Watson (cjwatson) on 2019-04-15
Changed in launchpad:
assignee: nobody → Colin Watson (cjwatson)
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Launchpad QA Bot (lpqabot) wrote :
Colin Watson (cjwatson) on 2019-05-07
tags: added: qa-ok
removed: qa-needstesting
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
removed: qa-ok
Colin Watson (cjwatson) on 2019-09-13
tags: added: qa-ok
removed: qa-needstesting
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
removed: qa-ok
Changed in launchpad:
status: In Progress → Fix Committed
Colin Watson (cjwatson) wrote :

This is safe to deploy because the new issueAccessToken method will fail with "RuntimeError: codehosting.git_macaroon_secret_key not configured" until we get that configured. I'll file a ticket for that.

tags: added: qa-ok
removed: qa-needstesting
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers