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

@fcus/ms-identity-nest

v0.1.5

Published

A nest.js wrapper for the node.js Microsoft Azure app registration

Downloads

102

Readme

MS Identity Nest

An implementation for the @azure/msal-node implementation using nest.js

How to use

This should pretty much work out-of-the-box with the default node.js setup (if your app runs on port 3000) that Azure provides, under the app registration menu:

"Quickstart" > "Web application" > "Node.js web"

Download the package, steal the settings, add them to the .env and it should work as the example.

Step 1: Install

Install the package

  • npm i --save @fcus/ms-identity-nest

Step 2a: Environment config

Set the environment variables. You can do this by creating an .env file with these properties

MS_IDENTITY_NEST_AUTHORITY=
MS_IDENTITY_NEST_CLIENT_ID=
MS_IDENTITY_NEST_CLIENT_SECRET=
MS_IDENTITY_NEST_LOG_LEVEL=3
MS_IDENTITY_NEST_REDIRECT_URI=

Step 2b: Environment config (alternative)

Or by providing a MsIdentityConfig through dependency injection

import { Module } from '@nestjs/common';
import { MsIdentityConfig } from './ms-identity.config';
import { MsIdentityService } from './ms-identity.service';

@Module({
  providers: [
    MsIdentityService,
    {
      provide: MsIdentityConfig,
      useValue: {
        authority: '',
        clientId: '',
        clientSecret: '',
        logLevel: 3,
        redirectUri: '',
      },
    },
  ],
})
export class MsIdentityModule {}

Step 3: Controller routes

Create a new nest.js controller or embed it in your existing AuthController

import { Controller, Get, Req, Res } from '@nestjs/common';
import { Request, Response } from 'express';
import { MsIdentityService } from './ms-identity.service';

@Controller()
export class MsIdentityController {
  constructor(private msIdentityService: MsIdentityService) {}

  @Get('/')
  async getAuthCodeUrl(@Res() res: Response) {
    const url = await this.msIdentityService.getAuthCodeUrl();
    res.redirect(url);
  }

  @Get('/redirect')
  async acquireTokenByCode(@Req() req: Request) {
    const result = await this.msIdentityService.acquireTokenByCode({
      requestQueryCode: req.query.code as any,
    });

    // Whichever logic you want to
    return result;
  }
}

Development

To do

  • [x] Port the node.js example to nest.js
  • [x] Extract the config to a class
  • [x] Create a fallback to .env for the config
  • [x] Set up Ava testing
  • [ ] Replace manual test with automated one
  • [ ] Thoroughly test with Ava