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

Support OAuth2 #43

Closed
ekryski opened this Issue Feb 7, 2016 · 1 comment

Comments

Projects
None yet
1 participant
@ekryski
Copy link
Member

ekryski commented Feb 7, 2016

We should leverage passport rather than write our own OAuth negotiation code. When a user authenticates we return the user id and a Feathers JWT so that the JWT can be used for further API access.

There are quite a few social sign on providers out there that support OAuth2. Most notably, Facebook, Github, Google, etc.

We can leverage the passport-<provider> modules and let the user pass in the Strategy and simply map the strategy to an OAuth2 service. This will get us very far, very quickly.

@ekryski ekryski added this to the 1.0 release milestone Feb 7, 2016

@ekryski ekryski referenced this issue Feb 7, 2016

Closed

Support multiple auth providers #6

5 of 5 tasks complete
@ekryski

This comment has been minimized.

Copy link
Member Author

ekryski commented Feb 7, 2016

This is working in the decoupling branch and is slated to merged pretty soon.

@ekryski ekryski referenced this issue Feb 12, 2016

Merged

Decoupling #49

@ekryski ekryski closed this Feb 12, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.