How to lookup a user using API with kid
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- PR merge metrics
- PR metrics pending
Description
Is similar to [this issue](https://github.com/keybase/client/issues/24614) but instead of using a PGP prefix is a kid. I need that because [Saltpack](https://saltpack.org/signing-format-v2) do not use a PGP key but a Ed25519 public key. Currently [user/lookup.json](https://keybase.io/docs/api/1.0/call/user/lookup) only support PGP fingerprints and, as shown in the other issue, suffixes, no Ed25519 keys/kids.
From [the source code](https://github.com/keybase/client/blob/38a96307aa34f4ebafff79aa45a7c6245dd2ae38/go/libkb/key_lookup.go#L49-L85) seems there is an undocumented "key/basics.json" endpoint and, unlike the other endpoint, It don't support CORS.
I can workaround the CORS issue by setting up a proxy on my server, but using this undocumented endpoint is fine?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading go/libkb/key_lookup.go around lines 49-85 and compare the documented user/lookup.json endpoint with the undocumented key/basics.json endpoint. Determine whether KID lookup and CORS support are intended, and establish the supported endpoint and behavior as the outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100