Snapcraft request user to login even if the user is logged in
Metadata
Current evaluation
UX request: snapcraft register-key re-prompts for login even when already logged in; reporter asks for an explanatory message about the extra ACL-scoped re-auth. Unlabelled, no maintainer response.
Suggested action: needs triage
Reason: The issue has no labels, zero comments, and no maintainer response after ~8 years, so it has clearly never been categorised — the default action for an unlabelled, unassessed issue. Code inspection confirms the request is still open rather than fixed: snapcraft/commands/keys.py:187-230 still deliberately deletes SNAPCRAFT_STORE_CREDENTIALS ('Registering a key requires a login with specific ACLs') and calls client.login(acls=['modify_account_key']), and no explanatory emit message exists anywhere in the tree (grep for 're-login'/'extra permissions'/'already logged in' returns no matches), so this cannot be closed as resolved. It is a small, well-described UX nit — a single emit.message before the prompt would satisfy it — but the re-prompt itself is by design, and related Launchpad bug #1634803 covers the same complaint and was reportedly discussed as by-design, which leaves some ambiguity about whether maintainers want any change at all.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
22
Quick Win:
10
Complexity:
18
Confidence:
68
Actionability:
58
|
needs triage | UX request: snapcraft register-key re-prompts for login even when already logged in; reporter asks for an explanatory message about the extra ACL-scoped re-auth. Unlabelled, no maintainer response. | |
| stealth/space-bunny-alpha |
Impact:
28
Quick Win:
14
Complexity:
38
Confidence:
89
Actionability:
82
|
close resolved | In 2017, register-key requested another Ubuntu One login immediately after login; the user was authenticated and registration eventually succeeded. The register-key login path was later corrected by PR #3809. | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
14
Staleness:
95
Complexity:
30
Confidence:
60
Support Request:
10
|
close stale | 2017 report that snapcraft register-key re-prompts for Ubuntu One login right after a successful snapcraft login; reporter suggests a clearer message. No labels, 0 comments, no maintainer activity for ~8 years; codebase since fully rewritten. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
100
Complexity:
15
Confidence:
95
Support Request:
10
|
close stale | Snapcraft prompts for login again immediately after successful login when registering a key. The report is 8 years old, unlabelled, and has no maintainer activity. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | UX bug where snapcraft prompts for login during key registration despite a recent successful login. No maintainer interaction, labels, or comments. Over 8 years old. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
100
Complexity:
15
Confidence:
90
Support Request:
10
|
close stale | Snapcraft prompts for login credentials during key registration despite a recent successful login. Issue remains untriaged and completely inactive for over 8 years. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Duplicate Of:
snapcraft (launchpad)#1634803
(confidence 72%)
Prior bug 'snapcraft register-key doesn't use U1 SSO login credentials' reports the identical re-login-on-register-key behaviour; current keys.py still deliberately unsets credentials and re-logins with a modify_account_key-scoped token.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1634803 snapcraft register-key doesn't use U1 SSO login credentials | snapcraft (launchpad) | open | 2016 report that `snapcraft register-key` re-prompts for U1 SSO login even after `snapcraft login`. Discussed as by-design (fresh modify_account_key-scoped login); current keys.py still deliberately unsets credentials and re-logins. |