Comments (3)
Function based secret is supported by the request.jwtVerify() and reply.jwtSign() methods and is called with request, token, and callback parameters.
I would say that it is a correct behavior since the document already told you function based secret only supported by the above two methods.
from fastify-jwt.
Can you provide a full reproducible code snippet?
The secret
function is not called by fast-jwt
directly but inside this library.
from fastify-jwt.
import Fastify, { FastifyInstance, FastifyRequest } from "fastify";
import fastifyJwt, { TokenOrHeader } from "@fastify/jwt";
const server: FastifyInstance = Fastify({
logger: true
});
server.register(fastifyJwt, {
secret: async (request: FastifyRequest | TokenOrHeader) => {
console.log(request);
return "secret";
}
});
server.get("/test", (request, reply) => {
const token = server.jwt.sign({ userId: 12 }, { expiresIn: "2h" });
reply.send(token);
});
/**
* 服务启动
* @param port 端口
*/
const startServer = async (port: number) => {
try {
await server.listen({ port });
} catch (err) {
server.log.error(err);
process.exit(1);
}
};
startServer(3000)
from fastify-jwt.
Related Issues (20)
- Add documentation about changes in fastify.jwt object while using namespaces HOT 3
- cannot install it from yarn
- Bump version to notify users of fast-jwt breaking change
- Improve fastify.jwt.verify by either making errors easier to handle via callback, or returning a promise. HOT 1
- Remove conditional `jwtDecode` decorator or fix the docs HOT 3
- Authorization token is invalid: The iss claim value is not allowed error even though iss is specified at startup HOT 1
- Local sign options overwrites global sign options HOT 1
- `key` option is not defined in the types
- Allow a grace period for expired tokens to account for network latency HOT 3
- Add 'validate' option to allow token claim validation HOT 2
- [Docs] Missing extractToken option HOT 1
- If `authorization` is not of type Bearer to ignore it and check the cookie HOT 1
- The lookupToken function doesn't seem to receive the cookie options. HOT 3
- `FastifyInterface` TypeScript augmentation when using namespaces HOT 3
- Add request.user property only to routes with fastify.authenticate hook applied in Typescript HOT 1
- How should the namespace work? HOT 1
- Argument of type FastifyJwt is not assignable to parameter of type FastifyPluginAsync HOT 1
- "authenticate" example creates a new verifier instance and a new cache instance for each request HOT 1
- Repository permission issue HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fastify-jwt.