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

@lyvly/graphql-compose-auth-middleware

v1.0.1

Published

Provides middleware for custom authorization of graphql-compose queries

Downloads

5

Readme

graphql-compose-auth-middleware

npm version CircleCI

Provides custom middleware that can be used to authorize your services.

Motivation

We use these authorizers everywhere to ensure that our various GraphQL resolvers can only be accessed by the correct people with the correct authorizers. We thought it would be a good idea to expose these simple authorizers for you to gain inspiration from or to use in your project.

Usage

To use this library, add the main authorize function as middleware to your resolver definition in the schemaComposer and then pick any of our authorizers or write your own that follows our spec!

_Note: authorize() currently works on a first past the post system, the first authorizer that succeeds will be the context used for the rest of that request, it is advisable to order your authorizers from least privilege to most privilege at this time`

Feel free to open a PR and suggest a better or different way of doing things!

Example usage of one of our authorizers here

import { authorize, customScopeAuthorizer } from '@lyvly/graphql-compose-auth-middleware';

schemaComposer.Mutation.addFields({
  memberCreateOne: MemberTypeComposer.getResolver('memberCreateOne', [
    authorize([customScopeAuthorizer('yourScope')]),
  ]),
});

Custom scope authorizer

The custom scope authorizer interrogates context.claims.scope, which is expected to be an array. It takes in a scopeName parameter for the scope you wish to allow access to your resolver.

customScope(scopeName)

Filter By Claim Value authorizer

The filter by claim value authorizer interrogates context.claims[claimName]. If it exists, the claim value is passed down to the resolver via a filter argument with the filterName as the key for the filter.

filterByClaimValue(claimName, filterName)

Group authorizer

The group filter interrogates context.claims[claimName], which is expected to be an array. It then checks to see if the groupName is included within the above interrogated value.

group(claimName, groupName)

Authorizer specification

Our spec is very simple, simply create a standard graphql-compose middleware function and utilise the data inside to determine whether someone is authorized or not. Then return an object with a property of the name authorized as a boolean, and if true the 4 graphql-compose arguments are required as well.

Pass that function to authorize() as shown in the example at the top and you should be good to go!

Take a peek at some of our authorizers if you want to see an example of passing parameters into the authorizer as well.

export const yourAuthorizer = (source, args, context, info) => {
  if (falseCondition) {
    return { authorized: false };
  }

  return {
    authorized: true,
    source,
    args,
    context,
    info,
  };
};