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

mongodb-token-resolver

v3.1.2

Published

auth token resolver with a mongodb-backend

Downloads

7

Readme

mongodb-token-resolver

Composant de persistance de jetons de sécurité et des données utilisateurs associées. Cette implémentation utilise un stockage sur mongodb. Ce composant s'utilise avec le module walnut-rest-security.

configuration

Le module s'appuie sur la connexion mongo existante dans le proket.

Exemple de configuration en production avec la connexion mongo par defaut :

// config-prod.js
//...
{
    packagePath : 'architect-mongodb-native',
    url: 'mongodb://db-customers-is-01.private-lan.bimedia-it.com:27017.../parametrage?autoReconnect=true',
    config: {
        readPreference: 'secondaryPreferred',
        native_parser: true,
        replicaSet: 'myreplset'
    }
},
{ 
    packagePath : 'mongodb-token-resolver',
    collectionName: 'sessions'
},
//...

Si il y a plusieurs connexion mongo configurées dans le projet il faut indiquer au module nom de la connexion à utiliser.

Par exemple :

// config-prod.js
//...
{
    packagePath : 'architect-mongodb-native',
    parametrage : {
        url: 'mongodb://db-customers-is-01.private-lan.bimedia-it.com:27017.../parametrage?autoReconnect=true',
    },
    sales : {
        url: 'mongodb://db-customers-is-01.private-lan.bimedia-it.com:27017.../sales?autoReconnect=true',
    },
    config: {
        readPreference: 'secondaryPreferred',
        native_parser: true,
        replicaSet: 'myreplset'
    }
},
{ 
    packagePath : 'mongodb-token-resolver',
    collectionName: 'sessions',
    dbName: 'parametrage'
},
//...

upgrading from 1.x.x

La version précédente du module embarquait directement le pool de connexion mongo. Il fallait donc configurer l'url de connexion dans la config du module mongodb-token-resolver.

Désormais le module s'appuie sur le module architect qui doit être présent dans le projet.

Par exemple la config suivante était valide en version 1.x.x :

{
    packagePath: 'mongodb-token-resolver',
    url: 'mongodb://db-customers-is-02...27017/parametrage?autoReconnect=true',
    dbconfig: {
        readPreference: 'secondraryPreferred',
        native_parser: true,
        replicaSet: 'myreplset'
    },
    collectionName: 'sessions'
},

Il faut ajouter explicitement le module architect-mongodb-native dans le projet si il n'est pas déjà présent et configurer la connexion pour acceder aux sessions :

{
    packagePath : 'architect-mongodb-native',
    url: 'mongodb://db-customers-is-02...27017/parametrage?autoReconnect=true',
    config: {
        readPreference: 'secondaryPreferred',
        native_parser: true,
        replicaSet: 'myreplset'
    },
}, {
    packagePath: 'mongodb-token-resolver',
    collectionName: 'sessions'
}