arkerone / fastify-api-key

Fastify plugin to authenticate HTTP requests based on api key and signature

Hey 👋, I'm Axel Shaïta !

I'm a freelance backend developer & french blogger

Latest Blog Posts 📩

• À la découverte de…AdonisJS
• Clarifiez les décisions techniques avec les ADRs
• TypeScript : Programmation de types
• Logging Node.js avec Pino
• Docker : conteneuriser son application

fastify-api-key's Issues

Is there a way for server to enforce the headers?

Thank you for this plugin. I've been looking over the code and wondering if there's a way to specify a minimum list of headers that the server can require in the plugin. If I'm reading the code correctly, it appears the client can choose which headers are used to calculate the HMAC and the server won't enforce any minimum set of headers while parsing the Auth string. Did I misunderstand that?

My concern is this could lead to a downgrade attack, where an incorrectly configured client could just specify fewer fields, and the server would happily honor the request. I assume specifying more fields means you potentially have more entropy and the hmac is more resistant to attacks?

Also if I understand the spec correctly, one would need to issue an OPTIONS request, much like CORS, to get a list of the headers needed for the signature?

Can't be used with fastify > v4

fastify-plugin: fastify-api-key - expected '3.x' fastify version, '4.3.0' is installed