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

Security question (concerns) #143

Open
co-dax opened this issue Dec 14, 2023 · 1 comment
Open

Security question (concerns) #143

co-dax opened this issue Dec 14, 2023 · 1 comment

Comments

@co-dax
Copy link

co-dax commented Dec 14, 2023

How secure it the pattern used behind the button "continue with facebook" when used log into my application and then communicate with the backend server if all we get as authentication result is the email address and based on that we create the user account or log in. I mean, everyone even without using facebook sign-in workflow can post a xhr request to the server with an arbitrary email address and sign in with whatevery email address is used in the request payload?

Am I missing something? Is there some kind of token in the authentication response that I should pass to the backend server and then use it from there to communicate with facebook to make sure (that is, validate) and get confirmation from facebook that it has actually performed related authentication request?

Thanks!

@co-dax
Copy link
Author

co-dax commented Dec 14, 2023

Could an approach be to just pass access token to the backend and then try calling facebook graph api with that access token and if the token is valid then we are sure there actually has been a successful login request for that facebook user on the UI/client?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant