user key with account-key-request present in the store but no matching account-key
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snap Store Server |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
We have a case of a user that is trying to register a key but that fails, it turns out there's already an account-key-request for it, but not matching account-key, also the api doesn't list it as registered:
>curl -s -H "Accept: application/
type: account-key-request
public-
account-id: ipXkEKZQKS5Ud1R
name: default
since: 2017-02-
body-length: 717
sign-key-sha3-384: 9rrxV3xRkNjih58
...
but
>curl -s -H "Accept: application/
{"detail":"no assertion with type \"account-key\" and key {\"public-
I don't know/remember enough details of the process to know how this can have transpired, or how to fix it
tags: | added: account-key |
Changed in snapstore: | |
assignee: | Colin Watson (cjwatson) → nobody |