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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 22, 2022. It is now read-only.
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 🤷.
The text was updated successfully, but these errors were encountered:
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 🤷.
The text was updated successfully, but these errors were encountered: