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

logmein-webclient-be

v0.1.15

Published

LogmeIn web client backend Node.js module

Downloads

3

Readme

LogmeIn web client backend Node.js module

LogmeIn OAuth 2.0 endpoint supports JavaScript-centric application. These applications may access the resource owner's data while the user is present by obtaining explicit authorization from it by using the OAuth2 implicit grant model from RFC 6749.

One important characteristic of these applications is that the cannot keep a secret, which means that the client secret cannot be used to stablish the authentication.

In order to cirnunvent this issue, the implicit grant model involves that the client should provide a callback endpoint on their web infrastructure.

This libray provides with the functionality for performing access_token validation from your web app backend as well as for retrieving resources from the authorization server.

Import and initialize the module

In order to use this module add it to your dependencies:

$ npm install logmein-client-validation --save

Inside your application code, import the token validator from the module:

var logmein = require('logmein-client-validation'),
    client = logmein();

If your client is using its own infrastructure, host, port and apiVersion can be passed to the logmein constructor as a configuration object.

Access token validation:

One important thing to take into account is that the client should always validate the access_token once retrieved from the authorization server. Failure to do so makes your application more vulnerable to the confused deputy problem.

This module provides with the validateToken method that can be used as follows:

client.validateToken(access_token,
            function(r) {
               // Save the access token in the session
               session.access_token = access_token;
               response.writeHead(200);
               response.end();
            },
            function(r) {
              // Return a token expired/invalid error
              response.writeHead(498);
              response.end();
            },
            function(e) {
              // An error happened
              response.writeHead(500);
              response.end(e);
            }
        );   

Accessing resource owner's data

Once the client has been granted access to the resource owner's resources and the token has been validated, it can access it by means of the getResource() method.

As a way of example, here's the JavaScript code in the browser to access the resource owner's profile data:

client.getResource(session.access_token, "/profile", undefined,
    function(r) {
        r.on('data', function(chunk) {
            profile = JSON.parse(chunk);
    },
    function(e) {
       // An error happened
    }
);