New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow login with decentralized identifier #1749
Comments
This issue has been automatically marked as stale because it has not had recent activity. We want to keep it in our todo list but haven't had the time to address it yet. |
I think the idea of using blockstack is great. I wonder if they might be able to put a bounty on it. |
I'm asking Patrick Stanley @ blockstack if they are interested in placing a bounty for it. We can't this on right now ourselves and we don't have the expertise. |
There is a bounty of $500 if done by 4th June (https://community.blockstack.org/evil/) I started some work on https://github.com/friedger/opencollective-frontend Help welcome! |
For the backend, I suggest that the signin request returns an encrypted signin link if a public key was provided:
|
In opencollective/opencollective-api#2034 the suggested addition of publicKey has been implemented. Both PRs together creates a flow where users can login with their Blockstack ID. |
This issue has been automatically marked as stale because it has not had recent activity. We want to keep it in our todo list but haven't had the time to address it yet. |
User story
As user, I can login with my own identity so that I don't have to use passwords
Best solution for this problem
Support universal identity resolver like https://github.com/decentralized-identity/universal-resolver/
MVP
Metrics
Usage of sign in with blockstack id
Documentation
Integration for the front end is described on docs.blockstack.org
Integration for the server is not clear to me, as I haven't found the location of the authentication flow
This tries to improve the authentication like #1738 and #1746
Details for MVP
Front end
Back end
user.publicKey
on backendThe text was updated successfully, but these errors were encountered: