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
Spent a lot of time with debugging and looking for a problem with @next version:
I used a lot of strategies(local, JWT...) with passed callback in passport.authenticate function and can't understand why (error, user) => { } parameters in the callback works so unpredictable.
For example, I've passed such arguments to the done callback in the strategy: done(null, user); after that passport.authenticate callback will be called with (user, undefined).
So I have to pass such arguments to make it work properly: done(null, null, user) or done(null, error). Sometimes, some of the parameters set to false. There's no such errors in main version of koa-passport!
The text was updated successfully, but these errors were encountered:
Spent a lot of time with debugging and looking for a problem with @next version:
I used a lot of strategies(local, JWT...) with passed callback in
passport.authenticate
function and can't understand why(error, user) => { }
parameters in the callback works so unpredictable.For example, I've passed such arguments to the done callback in the strategy:
done(null, user);
after that passport.authenticate callback will be called with(user, undefined).
So I have to pass such arguments to make it work properly:
done(null, null, user)
ordone(null, error)
. Sometimes, some of the parameters set to false. There's no such errors in main version of koa-passport!The text was updated successfully, but these errors were encountered: