Research
Security News
Malicious npm Package Targets Solana Developers and Hijacks Funds
A malicious npm package targets Solana developers, rerouting funds in 2% of transactions to a hardcoded address.
passport-headerapikey
Advanced tools
Api key authentication strategy for Passport, which only handles headers (not body fields).
The passport-headerapikey npm package is a Passport strategy for authenticating with an API key passed in a header. It allows you to protect your routes by requiring a valid API key for access.
Basic API Key Authentication
This feature allows you to set up basic API key authentication using the passport-headerapikey strategy. The provided code demonstrates how to configure the strategy and protect a route in an Express application.
const passport = require('passport');
const HeaderAPIKeyStrategy = require('passport-headerapikey').HeaderAPIKeyStrategy;
passport.use(new HeaderAPIKeyStrategy(
{ header: 'Authorization', prefix: 'Api-Key ' },
false,
(apikey, done) => {
if (apikey === 'your_api_key') {
return done(null, true);
} else {
return done(null, false);
}
}
));
// Express setup
const express = require('express');
const app = express();
app.use(passport.initialize());
app.get('/protected', passport.authenticate('headerapikey', { session: false }), (req, res) => {
res.send('This is a protected route');
});
app.listen(3000, () => {
console.log('Server is running on port 3000');
});
The passport-http-bearer package is a Passport strategy for authenticating with a bearer token. It is similar to passport-headerapikey in that it allows you to protect routes using a token, but it uses the Bearer token scheme instead of a custom header.
The passport-custom package allows you to create custom authentication strategies. It provides more flexibility compared to passport-headerapikey, as you can define your own logic for extracting and validating credentials from the request.
Passport strategy for authenticating with a apikey.
This module lets you authenticate using a apikey in your Node.js applications which is used to build rest apis. By plugging into Passport, apikey authentication can be easily and unobtrusively integrated into any application or framework that supports Connect-style middleware, including Express.
$ npm install passport-headerapikey
The api key authentication strategy authenticates users using a apikey.
The strategy requires a verify
callback, which accepts these
credentials and calls done
providing a user.
const HeaderAPIKeyStrategy = require('passport-headerapikey').HeaderAPIKeyStrategy
passport.use(new HeaderAPIKeyStrategy(
{ header: 'Authorization', prefix: 'Api-Key ' },
false,
function(apikey, done) {
User.findOne({ apikey: apikey }, function (err, user) {
if (err) { return done(err); }
if (!user) { return done(null, false); }
return done(null, user);
});
}
));
Use passport.authenticate()
, specifying the 'headerapikey'
strategy, to
authenticate requests.
For example, as route middleware in an Express application:
app.post('/api/authenticate',
passport.authenticate('headerapikey', { session: false, failureRedirect: '/api/unauthorized' }),
function(req, res) {
res.json({ message: "Authenticated" })
});
new HeaderAPIKeyStrategy(header, passReqToCallback, verify);
Arguments:
headerConfig
(Object):
header
(String): name of the header field to be used for api keys, default: X-Api-Key.prefix
(String): prefix to be used in content of the header, eg. Bearer adsfadsfa
, default: empty. Attention: give it with blank if needed, eg. 'Bearer '
.passReqToCallback
(Boolean): flags whether an express Request object is passed to the verify function.verify
(Function):
apiKey
(String): parsed API key from from the request. Use it to determine, which user is using your endpoint.verified
(Function): Callback to be called when you have done the API key handling. Signature: verify(err, user, info) => void
.
err
(Error): return an Error if user is not verified, otherwise yield null
hereuser
(Object, optional): only return user object if he is verified.info
(Object, optional): yield additional information to success or failure of user verification.req
(express.Request, optional): express Request object if passReqToCallback
is set to true.curl -v --header "Authorization: Api-Key asdasjsdgfjkjhg" http://127.0.0.1:3000/api/authenticate
Clone the repo, then
npm install
and here we go.
Develop your new features or fixes, test it using npm test
and create a pull request.
FAQs
Api key authentication strategy for Passport, which only handles headers (not body fields).
We found that passport-headerapikey demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
A malicious npm package targets Solana developers, rerouting funds in 2% of transactions to a hardcoded address.
Security News
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.