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

client side authentication #697

Closed
lean opened this issue Sep 6, 2018 · 3 comments
Closed

client side authentication #697

lean opened this issue Sep 6, 2018 · 3 comments

Comments

@lean
Copy link

lean commented Sep 6, 2018

I have a simple question. If I have authentication only on the client side, the scenario could be from a SPA, a mobile application, using hello.js or Firebase Authentication. What would be the best way to handle this?

@daffl
Copy link
Member

daffl commented Sep 6, 2018

Unfortunately this simple question does not have a simple answer 😉 There are many different ways to approach this but in any case, the server needs a way to verify the authentication information with the remote provider. What does the library/service you are using recommend for this?

@lean
Copy link
Author

lean commented Sep 6, 2018

I'm get the credentials of Google with the Google oAuth Sign-in / Log-in. In react for example: https://www.npmjs.com/package/react-google-login
If I verify the user credentials with google-auth-library, how could I handle the user registration/session?

@daffl
Copy link
Member

daffl commented May 8, 2019

This should be more easily possible now with Feathers v4 authentication where additionally to oAuth browser redirect the oAuth strategies can also be used with an existing oAuth access token.

Please see the migration guide for more information. Closing this issue in order to archive this repository. Related issues can be opened at the new code location in the Feathers main repository.

@daffl daffl closed this as completed May 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants