using fastify-passport with passport-jwt strategy about fastify-passport

[is2ei]

@mkgn

Is this call back needed (as per passport-jwt documentation?)

This question is not for fastify-passport. You should ask it in passport-jwt community.

---

Is below call back the proper place to validate the jwt and authenticate user against database?

The purpose of callback option is described in the README.

https://github.com/fastify/fastify-passport#authenticatestrategy-string--strategy--string--strategy-options-authenticateoptions-callback-authenticatecallback

An optional callback can be supplied to allow the application to override the default manner in which authentication attempts are handled. The callback has the following signature:

---

My question is out of the two places (mentioned in Question -1 & Question -2) what is the correct place I should use to do the user authentication/validation.

Did you try registerUserDeserializer?

https://github.com/fastify/fastify-passport#registeruserdeserializerdeserializer-serializeduser-request--promise

Registers an async user deserializer function for taking a low level serialized user object (often just a user ID) from a session, and deserializing it from storage into the request context. @fastify/passport cannot store rich object classes in the session, only JSON objects, so you must register a serializer / deserializer pair if you want to say fetch a User object from your database, and store only a user ID in the session.

[mkgn]

Sorry it's difficult to sometimes understand where the question should go to because this plugin is pretty much tight to passport.js. I will try it there. Meanwhile I used fastify/jwt and got the job done until I resolve this.