npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

passport-gitlub

v1.0.2

Published

GitLub authentication strategy for Passport.

Downloads

5

Readme

passport-gitlub

Forked from github.com/fh1ch/passport-gitlab2 But modified to work with Gitlub

npm version Dependency Status

Passport strategy for authenticating with Gitlub using the OAuth2 authentication provider service.

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

Install

$ npm install passport-gitlub

Usage

Before using the OAuth2 authentication provider service, you have register a new application in your user profile. GitLub will then issue an application ID and a secret, which need to be provided to the strategy. You will also need to configure a redirect URI which matches the route in your application.

Configure Strategy

The Gitlub authentication strategy authenticates users using a Gitlub account and OAuth 2.0 tokens. The app ID and secret obtained when creating an application are supplied as options when creating the strategy. The strategy also requires a verify callback, which receives the access token and optional refresh token, as well as profile which contains the authenticated user's GitLab profile. The verify callback must call cb providing a user to complete authentication.

passport.use(new GitLubStrategy({
    clientID: GITLUB_APP_ID,
    clientSecret: GITLUB_APP_SECRET,
    callbackURL: "http://localhost:3000/auth/gitlub/callback"
  },
  function(accessToken, refreshToken, profile, cb) {
    User.findOrCreate({gitlubId: profile.id}, function (err, user) {
      return cb(err, user);
    });
  }
));

Authenticate Requests

Use passport.authenticate(), specifying the 'gitlub' strategy, to authenticate requests.

For example, as route middleware in an Express application:

app.get('/auth/gitlub', passport.authenticate('gitlub'));

app.get('/auth/gitlub/callback', passport.authenticate('gitlub', { failureRedirect: '/login' }), (req, res) => {
    // Successful authentication, redirect home.
    res.redirect('/');
});

FAQ

How do I change permissions / scope when obtaining a user profile?

Gitlub supports two scopes at the moment which are read_user and api. By default, the read_user scope is used which was introduced with Gitlub version 8.15 and requires at least this version. If you have an older version or you need full read/write access to all API resources, use the api scope instead. Changing the OAuth2 scope to api works as following:

app.get('/auth/gitlub', passport.authenticate('gitlub', { scope: ['api'] }));

More information can be found in the official GitLab documentation.

License

The MIT License

Copyright (c) 2016-2017 Fabio Huser [email protected]

Copyright (c) 2011-2016 Jared Hanson <http://jaredhanson.net/>