These are chat archives for waterlock/waterlock

8th
Oct 2015
Wayne Douglas
@wayne-o
Oct 08 2015 09:08
You can specify JWT as the response from succesful login in the waterlock.config file:

    // post login event
    login: {

      // This can be any one of the following
      //
      // url - 'http://example.com'
      // relativePath - '/blog/post'
      // obj - {controller: 'blog', action: 'post'}
      // string - 'custom json response string'
      // default - 'default'
      success: 'jwt',

      // This can be any one of the following
      //
      // url - 'http://example.com'
      // relativePath - '/blog/post'
      // obj - {controller: 'blog', action: 'post'}
      // string - 'custom json response string'
      // default - 'default'
      failure: 'default'
    }
This circumvents session
Chris LeBlanc
@spacesuitdiver
Oct 08 2015 15:50
Ah... I saw that but had no idea what that stuff did as the term "event" drew me away (I figured it was just a way to do some sort of post-processing for tasks). Should document it as a "response" instead of "event".
Val Vinder
@mrvini
Oct 08 2015 16:14
@wayne-o - please let us know if you find an easy way to integrate sails-permissions without the need to bring the passport and sails-auth in. I'd be interested in this as well
Chris LeBlanc
@spacesuitdiver
Oct 08 2015 16:16
Are the routes documented somewhere? I'm looking through the source and am not sure if you add something to the route to accept say an access_token from Facebook. Also are routes configurable? I'm working through a swagger file I created and wanted to design the API my way and then map in all the waterlock stuff.
Chris LeBlanc
@spacesuitdiver
Oct 08 2015 16:26
Sorry I'll RTFM this time... some routes are documented here: (https://github.com/waterlock/waterlock-facebook-auth) , I'm guessing we could do vanity routes to change things up.
Wayne Douglas
@wayne-o
Oct 08 2015 18:51
@davidrivera has kindly given me access to NPM so I'll be pushing a new release as soon as I can get around to it :)