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
app.get("/protected",(req,res)=>{// calling this so as to catch error and respond without 500 and pass all the details to the user.passport.authenticate('facebook-token',{session: false},function(err,user,info){<function2>
...
are executed every time I do an HTTP GET for the "/protected" end point.
Is it the case that passport.authenticate() is what calls the strategy function?
Also under what conditions does the library ping facebook to validate the token?
I should think that if it is a known user and the time to live isn't expired we
shouldn't have to do a lookup.
The text was updated successfully, but these errors were encountered:
Yeah... I was also thinking about that.
This strategy is called everytime we try to access a protected data. So if a user is not registered and he calls this endpoint, it will create a new user. But I dont think I want to create a new user from all the calls. Also I want multiple providers in my server.
Hi I wrote an example server and client for your library.
One thing I am trying to figure out is, I noticed that both the
and
are executed every time I do an HTTP GET for the "/protected" end point.
Is it the case that passport.authenticate() is what calls the strategy function?
Also under what conditions does the library ping facebook to validate the token?
I should think that if it is a known user and the time to live isn't expired we
shouldn't have to do a lookup.
The text was updated successfully, but these errors were encountered: