
Security News
Risky Biz Podcast: Making Reachability Analysis Work in Real-World Codebases
This episode explores the hard problem of reachability analysis, from static analysis limits to handling dynamic languages and massive dependency trees.
passport-trusted-header
Advanced tools
passport.js strategy for authentication by a trusted HTTP header.
Node.js apps often have TLS handled by a front-end web server like nginx. For client cert authentication, the web server passes through certificate fields like DN as HTTP headers. The Node app can use these headers for authentication.
This library helps to do this with passport.js. If you have a Node.js app that accepts direct TLS connections, try passport-client-cert instead.
The connection between web server and web app must be secure. The front-end web server must whitelist HTTP headers to send to the web app, and it must be impossible for external processes to reach the web app or interfere with connections between the web server and Node.js. It is completely insecure if these conditions are not met!
Create the strategy with an options object and a "verify request" callback.
headers
- required. Array of HTTP header names to extract. A request has to contain all of these headers to be authenticated.passReqToCallback
- optional. Causes the request object to be supplied to the verify callback as the first parameter.The verify callback decides whether to authenticate each request. It called with the extracted header names/values and a passport.js done
callback.
var passport = require('passport');
var Strategy = require('passport-trusted-headers').Strategy;
var options = {
headers: ['TLS_CLIENT_DN']
}
passport.use(new Strategy(options, function(requestHeaders, done) {
var user = null;
var userDn = requestHeaders.TLS_CLIENT_DN;
// Authentication logic here!
if(userDn === 'CN=test-cn') {
user = { name: 'Test User' }
}
done(null, user);
}));
The verify callback can be supplied with the request
object by setting the passReqToCallback
option to true
, and changing callback arguments accordingly.
var options = {
headers: ['TLS_CLIENT_DN'],
passReqToCallback: true
}
passport.use(new Strategy(options, function(req, requestHeaders, done) {
var user = null;
var userDn = requestHeaders.TLS_CLIENT_DN;
// Authentication logic here!
if(userDn === 'CN=test-cn') {
user = { name: 'Test User' }
}
done(null, user);
}));
$ npm install
$ npm test
Contributions are welcome! Please write unit tests, follow the existing coding style and lint with eslint.
FAQs
Passport.js strategy for trusted HTTP headers
We found that passport-trusted-header 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.
Security News
This episode explores the hard problem of reachability analysis, from static analysis limits to handling dynamic languages and massive dependency trees.
Security News
/Research
Malicious Nx npm versions stole secrets and wallet info using AI CLI tools; Socket’s AI scanner detected the supply chain attack and flagged the malware.
Security News
CISA’s 2025 draft SBOM guidance adds new fields like hashes, licenses, and tool metadata to make software inventories more actionable.