You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be cool if keybase supported some sort of API for allowing sites to support verification.
Keybase would have a verification option where you supplied your username, and a link to the site's location for the api. Keybase would query that api with the username, and the site would return the user's proof. This way, keybase doesn't have to implement each site manually, instead allowing the sites themselves to support keybase.
The query would look something like this: GET https://domain.name/kbapi/proof/<username>
to which the site would respond with the same file that would normally go in .well-known.
Because the api would not require any authentication (it only serves static content), the proofs would be available to everyone.
The text was updated successfully, but these errors were encountered:
skwerlman
changed the title
Generic third-party verification api
third-party verification api
Apr 7, 2017
If I understand your suggestion correctly, I have been mulling a similar idea. I would like to be able to run an application on my company web site where I can easily create identity proofs for all my employees.
I don't think any special case needs to be added to Keybase to support this. It can just be a standard web identity verification, with Keybase CLI running on my web server alongside a simple web app where I can manage the users I want to prove. I could see that being a nice little open source project to complement Keybase.
If this is the kind of thing you are envisioning, I would be interested in discussing further.
It'd be cool if keybase supported some sort of API for allowing sites to support verification.
Keybase would have a verification option where you supplied your username, and a link to the site's location for the api. Keybase would query that api with the username, and the site would return the user's proof. This way, keybase doesn't have to implement each site manually, instead allowing the sites themselves to support keybase.
The query would look something like this:
GET https://domain.name/kbapi/proof/<username>
to which the site would respond with the same file that would normally go in
.well-known
.Because the api would not require any authentication (it only serves static content), the proofs would be available to everyone.
The text was updated successfully, but these errors were encountered: