Loopback: access_token null on custom middleware

Created on 21 May 2017 · 8Comments · Source: strongloop/loopback

server.js file:

app.use(cookieParser('secret'));
app.use(loopback.token({
  model: app.models.accessToken,
  cookies: ['access_token']
}));

custom middleware:

'use strict';
var user = require('../../common/proxies/UserProxy');

module.exports = status;
function status() {
  return function(req, res,next) {


    if (req.accessToken) { // access token is null 

      user.getProfile(req.accessToken.userId, function (user_res) {
        if (user_res.result) {
          next();

        }else{

          req.app.locals.msg = {
            hasMessage: true,
            Message: "",
            messageTitle: "",
            alertClassName: "alert-danger",
            app: req.app
          };

          res.redirect('/user/login');
        }
      });
  }else {

      req.app.locals.msg = {
        hasMessage: true,
        Message: "",
        messageTitle: "",
        alertClassName: "alert-danger",
        app: req.app
      };

      res.redirect('/user/login');

    }
  }


}

accesstoken is null in middleware , but work on route :(((

stale

Source

mahdinai

👍2

Most helpful comment

actually this is an excellent question : how to get current user in custom middleware ?

req.accessToken is always undefined

ydomenjoud on 21 Jun 2017

👍6

All 8 comments

Please Check the doc here ..
https://docs.strongloop.com/display/public/LB/Defining+middleware

yshing on 23 May 2017

actually this is an excellent question : how to get current user in custom middleware ?

req.accessToken is always undefined

ydomenjoud on 21 Jun 2017

👍6

In Loopback, there's not 1 kind of middleware, there's about 5. So you have to sort out what order they all run in and how they interact. Personally I dodged this complexity by wedging my own strategy in. Not ideal, but at least I can reason about the order things run in.

bitmage on 8 Aug 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] on 7 Oct 2017

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

stale[bot] on 21 Oct 2017