Add ability to prepend the header string to the token, before trying to decode it about passport-jwt HOT 3 CLOSED

Is this a common practice? What is driving this need? In my experience with using JWTs for authentication the JWT is provided in whole by the party being authenticated. Modifying the JWT as part of authentication seems odd.

I would suggest that you modify the partial JWT from the request before invoking this authentication module. The modified JWT can be added to the request object and you can use a custom extractor function to retrieve it and authenticate it with this module.

from passport-jwt.

The use case is to make slightly hard for an user to understand how the token is built (which sign algorithm). Not really odd, or yes?

I would suggest that you modify the partial JWT from the request

It looks like a good choice, so before invoking passport.authenticate('jwt', etc..

For anyone else:

if (req.headers.authorization)
    req.headers.authorization = "JWT " + header + req.headers.authorization;

passport.authenticate('jwt', etc...

Of course, after have modified how the client sends the token in the header and using the .fromAuthHeader() extractor

from passport-jwt.

@themikenicholson As you can see, a unified way for every extractor would be better

from passport-jwt.