Skip to content
This repository has been archived by the owner on Mar 22, 2022. It is now read-only.

Support OAuth1 #42

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

Support OAuth1 #42

ekryski opened this issue Feb 7, 2016 · 1 comment
Labels
Backlog Feature
Milestone
2.0

Comments

@ekryski
Copy link
Member

ekryski commented Feb 7, 2016 •
edited
Loading

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 🤷.
@ekryski ekryski mentioned this issue Feb 7, 2016
Closed
5 tasks
@ekryski ekryski mentioned this issue Feb 18, 2016
Closed
42 tasks
@ekryski ekryski added this to the 2.0 milestone May 21, 2016
@ekryski
Copy link
Member Author

ekryski commented Nov 21, 2016

This is now supported via feathers-authentication-oauth1

@ekryski ekryski closed this as completed Nov 21, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Backlog Feature
Projects
None yet
Milestone
2.0
Development

No branches or pull requests
1 participant
@ekryski