Gathering detailed insights and metrics for passport-google-oauth1
Gathering detailed insights and metrics for passport-google-oauth1
Gathering detailed insights and metrics for passport-google-oauth1
Gathering detailed insights and metrics for passport-google-oauth1
passport-oauth1
OAuth 1.0 authentication strategy for Passport.
passport-google-oauth
Google (OAuth) authentication strategies for Passport.
passport-oauth
OAuth 1.0 and 2.0 authentication strategies for Passport.
passport-google-oauth20
Google (OAuth 2.0) authentication strategy for Passport.
Google (OAuth 1.0) authentication strategy for Passport.
npm install passport-google-oauth1
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
4 Stars
14 Commits
1 Forks
4 Watching
1 Branches
2 Contributors
Updated on 14 Jun 2024
JavaScript (97.27%)
Makefile (2.73%)
Cumulative downloads
Total Downloads
Last day
-6.9%
10,490
Compared to previous day
Last week
-3.5%
53,387
Compared to previous week
Last month
15.8%
228,809
Compared to previous month
Last year
-12.8%
2,520,115
Compared to previous year
1
4
DEPRECATED: On April 20, 2015, Google's support for OAuth 1.0 was officially deprecated and is no longer supported. You are encouraged to migrate to OAuth 2.0 and passport-google-oauth20 as soon as possible.
Passport strategy for authenticating with Google using the OAuth 1.0a 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.
$ npm install passport-google-oauth1
Before using passport-google-oauth1
, you must register your domain with Google.
If you have not already done so, a new domain can be added at Google Accounts.
Your domain will be issued an OAuth Consumer Key and OAuth Consumer Secret,
which need to be provided to the strategy.
The Google authentication strategy authenticates users using a Google account
and OAuth tokens. The consumer key and consumer secret obtained when
registering a domain are supplied as options when creating the strategy. The
strategy also requires a verify
callback, which receives the access token and
corresponding secret as arguments, as well as profile
which contains the
authenticated user's Google profile. The verify
callback must call cb
providing a user to complete authentication.
passport.use(new GoogleStrategy({
consumerKey: 'www.example.com',
consumerSecret: GOOGLE_CONSUMER_SECRET,
callbackURL: "http://127.0.0.1:3000/auth/google/callback"
},
function(token, tokenSecret, profile, cb) {
User.findOrCreate({ googleId: profile.id }, function (err, user) {
return cb(err, user);
});
}
));
Use passport.authenticate()
, specifying the 'google'
strategy, to
authenticate requests.
For example, as route middleware in an Express application:
app.get('/auth/google',
passport.authenticate('google', { scope: 'https://www.google.com/m8/feeds' }));
app.get('/auth/google/callback',
passport.authenticate('google', { failureRedirect: '/login' }),
function(req, res) {
// Successful authentication, redirect home.
res.redirect('/');
});
Developers using the popular Express web framework can refer to an example as a starting point for their own web applications. The example shows how to authenticate users using Twitter. However, because both Twitter and Google use OAuth 1.0, the code is similar. Simply replace references to Twitter with corresponding references to Google.
The test suite is located in the test/
directory. All new features are
expected to have corresponding test cases. Ensure that the complete test suite
passes by executing:
1$ make test
All new feature development is expected to have test coverage. Patches that increse test coverage are happily accepted. Coverage reports can be viewed by executing:
1$ make test-cov 2$ make view-cov
This software is provided to you as open source, free of charge. The time and effort to develop and maintain this project is dedicated by @jaredhanson. If you (or your employer) benefit from this project, please consider a financial contribution. Your contribution helps continue the efforts that produce this and other open source software.
Funds are accepted via PayPal, Venmo, and other methods. Any amount is appreciated.
Copyright (c) 2012-2016 Jared Hanson <http://jaredhanson.net/>
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
Found 1/14 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
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