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 OAuth1 #42

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.

Most social sign on providers out there support OAuth2. The most prominent one that doesn't is Twitter. The trick with OAuth1 is that we need sessions, which kind of goes against the whole idea of using a JWT access token but :shrug:.

@ekryski ekryski referenced this issue Feb 7, 2016

Closed

Support multiple auth providers #6

5 of 5 tasks complete

@ekryski ekryski referenced this issue Feb 18, 2016

Closed

Generator for scaffolding a feathers app #159

42 of 42 tasks complete

@ekryski ekryski added the Feature label Mar 26, 2016

@ekryski ekryski added the Backlog label May 21, 2016

@ekryski ekryski added this to the 2.0 milestone May 21, 2016

@ekryski

This comment has been minimized.

Copy link
Member Author

ekryski commented Nov 21, 2016

This is now supported via feathers-authentication-oauth1

@ekryski ekryski closed this Nov 21, 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.
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.