Skip to content
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

User authentication #2

Open
lpatmo opened this issue Oct 18, 2019 · 2 comments
Open

User authentication #2

lpatmo opened this issue Oct 18, 2019 · 2 comments

Comments

@lpatmo
Copy link
Member

lpatmo commented Oct 18, 2019

My guess is https://docs.netlify.com/visitor-access/oauth-provider-tokens/ is the standard way to support user authentication. What are the alternatives?

@d3vild06
Copy link
Contributor

Yes, this is one option (and based on the docs very easy to implement!). I think we should come to a consensus on what provider we want our users to authenticate with for the site.

IMO, as a dev community, I feel it makes a ton of sense to use GitHub today. We can also pull in GH user info, such as commits to the CB repo and display them right in the site/profile!

@lpatmo
Copy link
Member Author

lpatmo commented Oct 21, 2019

++ to GitHub -- though folks may request an email/password option too. And using Identity makes the most sense if it's the standard way.

I like how easy Identity is to set up, but I noticed a couple of disadvantages with using it:
1/ We'll need to upgrade to a $45/mo pro plan (not covered under the open source plan) if we want to support role-based access control with JWT (e.g. having admins vs moderators vs normal users):
image
2/ Custom login branding isn't supported until we're under the $99/mo plan
3/ Identity is free up to 1000 active users. I'm not sure what "active" users mean -- logged-in users? I think at that level of activity we'd be able to cover the additional $99/mo with sponsors, but it's overhead at that size for sure.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants