Integration with glue

[no-more]

Hello,

Sorry for this newbie question but I couldn't figure out how to register and configure this plugin with glue manifest. I don't know what to put in options, I don't even know it this is possible with glue?

Thanks.

[nelsonic]

@no-more great question, really sorry that is unclear from our Docs.
At present this plugin does not support glue out-of-the-box.
are you using glue in your project...?

(only one other person has requested glue support, so it has not yet been a priority for us...)

[vdeturckheim]

I don't see any straightforward way to do this using Glue.
The solution I use and recommend is to build a plugin around hapi-auth-jwt2.
Take a look at this repo: https://github.com/vdeturckheim/sticky_auth
I created a plugin around hapi-auth-basic to assess my needs.

[vdeturckheim]

@nelsonic a glue usage out of the box seems complicated to me. At least it will need a very careful design since everyone is using a different database or have different need (I decorate my auth objects with scopes for instance).
A solution I see would be to let the conf object accept the reference to a node module exposing the functions needed:

{
    "functionsHome": "myFcts"
}

with myFcts being a module exposing a validate function.

However I see 2 enhancements we could easely make here:

• let use redis out of the box (just provide access to instance)
• allow to drop the following lines in favor of configuration:

    server.auth.strategy('jwt', 'jwt',
    { key: 'NeverShareYourSecret',          // Never Share your secret key
      validateFunc: validate,            // validate function defined above
      verifyOptions: { algorithms: [ 'HS256' ] } // pick a strong algorithm
    });

    server.auth.default('jwt');

[no-more]

Hi,

thanks for your fast answers, yes I'm currently using glue and try to put every plugin configuration within it.
I'm building it with a manifest.js file which allow me to put stuff dynamically within it, but I'm not sure if it's possible to define function in the final manifest file.
I think, but I'm not sure, I've seen something like this somewhere but can't find it anymore.

I'm quite new to nodejs & hapi, I'm just trying to build a boilerplate for my next project so I'm trying to find best practices, that's why I'm trying to use glue which seems to be the new way to do things in hapi.

Thanks.

[vdeturckheim]

The only time I've seen functions in manifest would be here https://github.com/hapijs/rejoice
There is a possibility for preConnections and preRegister method.
You can take a look at my sticky repos. I created them to show the use of Glue to @nelsonic actually ;)

[Miguel-Herrero]

Hi, I was considering using this plugin for my hapijs project, but as I'm using Glue and I read here that it's not supported, I don't know if I can plug it easily…

(I started using Glue because the official hapijs tutorial teaches to use it…)

[nelsonic]

@Miguel-Herrero glue is nice but fewer than 8% of Hapi projects use it...

[Miguel-Herrero]

Oh, I didn't know that @nelsonic Thanks for the info.

I guess a hapijs app is more configurable without Glue?

[nelsonic]

@Miguel-Herrero glue is a really nice way of composing your Hapi.js app.
Its just not used by that many apps/teams... I have been tempted to use it, but feel that I don't need an additional layer of abstraction when Hapi already allows me to write my app declaratively...
However, we could add glue support if more people request it...

[mikefrey]

I'd love to see glue support. We use rejoice which uses glue internally. It's a great way to force you to write everything in plugins, which in turn, forces you to design with modularity and maintainability in mind.

[avanslaars]

For what it's worth, I'd love to see glue support as well. I'm using it at work and on a personal project. If I find some free time and this still isn't a high priority, I may take a stab at this.

For the time being, I'm taking the advice of @vdeturckheim and have simply wrapped this in my own plugin like so:

'use strict'

const hapiJwt = require('hapi-auth-jwt2')
const JWT_SECRET_KEY = require('lg/lib/always').JWT_SECRET_KEY

const register = function register (server, options, next) {
  server.register(hapiJwt)
  server.auth.strategy('jwt', 'jwt',
  { key: JWT_SECRET_KEY,
    validateFunc: (decoded, request, callback) => callback(null, true), // This should be replaced with a more robust function
    verifyOptions: { algorithms: [ 'HS256' ] }
  })

  server.auth.default('jwt')
  next()
}

register.attributes = {
  name: 'auth-wrapper',
  version: '0.0.1'
}

module.exports = register

and then I can load this in my glue manifest like so:

...
registrations: [
    {
      plugin: {
        register: 'vision'
      }
    },
    {
      plugin: {
        register: './authWrapper'
      }
    },
    {
      plugin: {
        register: './PluginWithMyRoutesAndStuff'
      },
      options: {
        select: ['web']
      }
    }
...

[sean-hill]

@avanslaars I tried using your idea with glue, and I got my route to return a 401 response. However, I can't get the validateFunc to run or return true and allow access to my route. Have you had any luck there?

For testing I'm just using validateFunc: (decoded, request, callback) => callback(null, true) like your example.

[avanslaars]

@sean-hill It is working in my app. It's a WIP, so I haven't done anything with my validateFunc to change it from the example. I auth with githuub's OAuth api and create a token with the jsonwebtoken module. I am storing the auth token in a cookie called token. I then use the jwt auth strategy in my routes and it accepts the token.

// Create the token

const jwt = require('jsonwebtoken')
const JWT_SECRET_KEY = require('lg/lib/always').JWT_SECRET_KEY

// Code that handles OAuth, saving user in DB, etc...

const theToken = jwt.sign({name:'sample'}, JWT_SECRET_KEY)
return reply.redirect('/dashboard').state('token', theToken, {
   path: '/',
   ttl: 2592e5
})

Sample route that uses auth

server.route([{
    method: 'GET',
    path: '/dashboard',
    config: {
      auth: 'jwt'
    },
    handler: function (request, reply) {
      reply.view('dashboard')
    }
  }

If I have the cookie in place, this route works and if I delete the cookie, I get a 401.

I hope this helps.

[sean-hill]

@avanslaars thanks. I got it working :)