npmpackage.info

Gathering detailed insights and metrics for passport-google-verify-token

Other packages similar to passport-google-verify-token

passport-jwt

4.0.1

Passport authentication strategy using JSON Web Tokens

passport-oauth2

1.8.0

OAuth 2.0 authentication strategy for Passport.

passport-http-bearer

1.0.1

HTTP Bearer authentication strategy for Passport.

passport-oauth1

1.3.0

OAuth 1.0 authentication strategy for Passport.

Gathering detailed insights and metrics for passport-google-verify-token

passport-google-verify-token

Passport strategy for authenticating with Google access tokens using the OAuth 2.0 API.

3.0.5

TypeScript

172,833 3.4

Installations

npm install passport-google-verify-token

Score

52.2

Supply Chain

97.7

Quality

75.1

Maintenance

100

Vulnerability

98.9

License

Pull Requests

Open

1

Total

24

Closed

5

Merged

18

Issues

Open

2

Total

4

Closed

2

Releases

v3.0.5

Published on 27 Jun 2024

v3.0.4

Published on 27 Jun 2024

v3.0.3

Published on 27 Jun 2024

v3.0.2

Published on 27 Jun 2024

v3.0.1

Published on 26 Jun 2024

v2.3.3

Published on 09 Jan 2023

View all 17 releases

Developer

abouroubi

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

Yes

Node Version

20.10.0

NPM Version

10.8.1 Statistics

5 Stars

134 Commits

9 Forks

2 Watching

1 Branches

6 Contributors

Updated on 27 Jun 2024

Languages

TypeScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

172,833

Last day

15.1%

145

Compared to previous day

Last week

8.2%

859

Compared to previous week

Last month

-4.5%

3,703

Compared to previous month

Last year

15.3%

51,311

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

google-auth-library got passport-strategy

Dev Dependencies

@types/chai @types/mocha @types/node @types/passport-strategy chai chai-passport-strategy mocha mocha-junit-reporter nyc prettier rimraf ts-node tslint tslint-config-prettier typescript

Versions

passport-google-verify-token

Passport strategy for authenticating with Google access tokens using the OAuth 2.0 API.

This module lets you authenticate using Google in your Node.js applications. By plugging into Passport, Google authentication can be easily and unobtrusively integrated into any application or framework that supports Connect-style middleware, including Express.

Installation

$ npm install passport-google-verify-token

Usage

Configure Strategy

The Google authentication strategy leverages the Google Auth Library for Node.js to authenticates users. Applications must supply a verify callback which accepts the idToken or access_token coming from the user to be authenticated, and then calls the done callback supplying a parsedToken (with all its information in visible form) and the googleId.

1var GoogleTokenStrategy = require("passport-google-verify-token").Strategy;
2
3passport.use(new GoogleTokenStrategy({
4      clientID: '12345.abcdefghijkl.apps.googleusercontent.com'// Specify the CLIENT_ID of the backend
5     // If other clients (such as android / ios apps) also access the google api:
6     // audience: [CLIENT_ID_FOR_THE_BACKEND, CLIENT_ID_ANDROID, CLIENT_ID_IOS, CLIENT_ID_SPA]
7    },
8    function(parsedToken, googleId, done) {
9      User.findOrCreate(..., function (err, user) {
10        done(err, user);
11      });
12    }
13  ));

When verifying an idToken, the Google Auth library verifyIdToken() function is called, and the authentication is finished. When an access_token is passed, however, two steps have to be made:

The Google Auth getTokenInfo() function is called. This is to verify that the token is valid and not expired.
A request to /oauth2/v3/userinfo is sent. access_tokens require this second step in order to get the same user information idTokens return.

Authenticate Requests

Use passport.authenticate(), specifying the 'google-verify-token' strategy, to authenticate requests.

1app.post('/auth/google/token',
2  passport.authenticate('google-verify-token'),
3  function (req, res) {
4    // do something with req.user
5    res.send(req.user? 200 : 401);
6  }
7);

Or using Sails framework:

1// api/controllers/AuthController.js
2module.exports = {
3  facebook: function(req, res) {
4    passport.authenticate('google-verify-token', function(error, user, info) {
5      // do stuff with user
6      res.ok();
7    })(req, res);
8  }
9};

Client Requests

Clients can send requests to routes that use google-verify-token authentication using query parms, body, or HTTP headers. Clients will need to transmit the access_token or the id_token that are received from Google after user logs in.

Sending access_token as a Query parameter

GET /auth/google/token?access_token=<TOKEN_HERE>

Sending access token as an HTTP header

Clients can choose to send the access token using the Oauth2 Bearer token (RFC 6750) compliant format

GET /resource HTTP/1.1
Host: server.example.com
Authorization: Bearer base64_access_token_string

Sending access token as an HTTP body

Clients can transmit the access token via the body

POST /resource HTTP/1.1
Host: server.example.com

access_token=base64_access_token_string

Credits

Abdou BOUROUBI

Thanks

This project is inspired by Juanma Reyes' Passport Google Id Token.

License

The MIT License (MIT)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

9

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

5

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 5

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-npm.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/abouroubi/passport-google-verify-token/publish-npm.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-npm.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/abouroubi/passport-google-verify-token/publish-npm.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/abouroubi/passport-google-verify-token/release.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/abouroubi/passport-google-verify-token/release.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/abouroubi/passport-google-verify-token/release.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:38: update your workflow using https://app.stepsecurity.io/secureworkflow/abouroubi/passport-google-verify-token/release.yml/master?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/release.yml:44: update your workflow using https://app.stepsecurity.io/secureworkflow/abouroubi/passport-google-verify-token/release.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:58: update your workflow using https://app.stepsecurity.io/secureworkflow/abouroubi/passport-google-verify-token/release.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:60: update your workflow using https://app.stepsecurity.io/secureworkflow/abouroubi/passport-google-verify-token/release.yml/master?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/release.yml:64: update your workflow using https://app.stepsecurity.io/secureworkflow/abouroubi/passport-google-verify-token/release.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/abouroubi/passport-google-verify-token/test.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/abouroubi/passport-google-verify-token/test.yml/master?enable=pin
Info: 0 out of 10 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 2 third-party GitHubAction dependencies pinned
Info: 4 out of 4 npmCommand dependencies pinned

1

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

License

Determines if the project has defined a license.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

3.4

/10

Last Scanned on 2024-11-25

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