Gathering detailed insights and metrics for passport-http-bearer
Gathering detailed insights and metrics for passport-http-bearer
HTTP Bearer authentication strategy for Passport and Node.js.
Installations
npm install passport-http-bearerReleases
Unable to fetch releases
Developer
Developer Guide
BETA
Module System
CommonJS
Min. Node Version
>= 0.4.0
Typescript Support
No
Node Version
NPM Version
1.2.25
Statistics
952 Stars
354 Commits
143 Forks
15 Watching
3 Branches
6 Contributors
Updated on 27 Nov 2024
Languages
JavaScript (91.41%)
Makefile (8.59%)
Total Downloads
Cumulative downloads
Total Downloads
51,622,172
Last day
-4%
51,265
Compared to previous day
Last week
3.1%
284,468
Compared to previous week
Last month
21%
1,125,378
Compared to previous month
Last year
0.3%
10,981,438
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
1
Dev Dependencies
3
Versions
passport-http-bearer
HTTP Bearer authentication strategy for Passport.
This module lets you authenticate HTTP requests using bearer tokens, as specified by RFC 6750, in your Node.js applications. By plugging into Passport, bearer token support can be easily and unobtrusively integrated into any application or framework that supports Connect-style middleware, including Express.
:hammer_and_wrench: API Reference • :heart: Sponsors
Advertisement
Node.js, Express, MongoDB & More: The Complete Bootcamp 2020
Master Node by building a real-world RESTful API and web app (with authentication, Node.js security, payments & more)
Install
$ npm install passport-http-bearer
TypeScript support
1$ npm install @types/passport-http-bearer
Usage
Configure Strategy
The HTTP Bearer authentication strategy authenticates users using a bearer
token. The strategy requires a verify callback, which accepts that
credential and calls done providing a user. Optional info can be passed,
typically including associated scope, which will be set by Passport at
req.authInfo to be used by later middleware for authorization and access
control.
1passport.use(new BearerStrategy(
2 function(token, done) {
3 User.findOne({ token: token }, function (err, user) {
4 if (err) { return done(err); }
5 if (!user) { return done(null, false); }
6 return done(null, user, { scope: 'all' });
7 });
8 }
9));Authenticate Requests
Use passport.authenticate(), specifying the 'bearer' strategy, to
authenticate requests. Requests containing bearer tokens do not require session
support, so the session option can be set to false.
For example, as route middleware in an Express application:
1app.get('/profile', 2 passport.authenticate('bearer', { session: false }), 3 function(req, res) { 4 res.json(req.user); 5 });
Issuing Tokens
Bearer tokens are typically issued using OAuth 2.0. OAuth2orize is a toolkit for implementing OAuth 2.0 servers and issuing bearer tokens. Once issued, this module can be used to authenticate tokens as described above.
Making authenticated requests
The HTTP Bearer authentication strategy authenticates requests based on a bearer token contained in the:
Authorizationheader field where the value is in the format{scheme} {token}and scheme is "Bearer" in this case.- or
access_tokenbody parameter - or
access_tokenquery parameter
Examples
For a complete, working example, refer to the Bearer example.
Related Modules
- OAuth2orize — OAuth 2.0 authorization server toolkit
License
Copyright (c) 2011-2013 Jared Hanson <https://www.jaredhanson.me/>
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
8 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-9vvw-cc9w-f27h
- Warn: Project is vulnerable to: GHSA-gxpj-cx7g-858c
- Warn: Project is vulnerable to: GHSA-h6ch-v84p-w6p9
- Warn: Project is vulnerable to: GHSA-qh2h-chj9-jffq
- Warn: Project is vulnerable to: GHSA-hxm2-r34f-qmc5
- Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
- Warn: Project is vulnerable to: GHSA-vh95-rmgr-6w4m / GHSA-xvch-5gv4-984h
- Warn: Project is vulnerable to: GHSA-w9mr-4mfr-499f
Reason
dependency not pinned by hash detected -- score normalized to 1
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js-eol-20140731.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport-http-bearer/node.js-eol-20140731.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js-eol-20140731.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport-http-bearer/node.js-eol-20140731.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js-eol-20190430.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport-http-bearer/node.js-eol-20190430.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js-eol-20190430.yml:28: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport-http-bearer/node.js-eol-20190430.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js-eol-20230430.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport-http-bearer/node.js-eol-20230430.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js-eol-20230430.yml:32: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport-http-bearer/node.js-eol-20230430.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js-eol.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport-http-bearer/node.js-eol.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js-eol.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport-http-bearer/node.js-eol.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport-http-bearer/node.js.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node.js.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport-http-bearer/node.js.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/nvm-manual.yml:35: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport-http-bearer/nvm-manual.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/nvm.yml:32: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport-http-bearer/nvm.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/nvm.yml:41: update your workflow using https://app.stepsecurity.io/secureworkflow/jaredhanson/passport-http-bearer/nvm.yml/master?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/node.js-eol-20140731.yml:38
- Warn: npmCommand not pinned by hash: .github/workflows/node.js-eol-20190430.yml:32
- Warn: npmCommand not pinned by hash: .github/workflows/node.js-eol-20230430.yml:40
- Warn: downloadThenRun not pinned by hash: .github/workflows/nvm-manual.yml:37
- Warn: npmCommand not pinned by hash: .github/workflows/nvm.yml:50
- Info: 0 out of 12 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 third-party GitHubAction dependencies pinned
- Info: 2 out of 6 npmCommand dependencies pinned
- Info: 0 out of 1 downloadThenRun dependencies pinned
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
no SAST tool detected
Details
- Warn: no pull requests merged into dev branch
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/node.js-eol-20140731.yml:1
- Warn: no topLevel permission defined: .github/workflows/node.js-eol-20190430.yml:1
- Warn: no topLevel permission defined: .github/workflows/node.js-eol-20230430.yml:1
- Warn: no topLevel permission defined: .github/workflows/node.js-eol.yml:1
- Warn: no topLevel permission defined: .github/workflows/node.js.yml:1
- Warn: no topLevel permission defined: .github/workflows/nvm-manual.yml:1
- Warn: no topLevel permission defined: .github/workflows/nvm.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Score
3.7
/10
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More