Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript User Authentication With Express and Mongo Improving the App with Custom Middleware Writing More Middleware

Kenneth Baur
Kenneth Baur
12,400 Points
Posted by Kenneth Baur
Kenneth Baur
12,400 Points

Why not check for userId session instead?

function requiresLoggedIn(req, res, next){
    if (req.session.userId){
        return next();
    }else{
        var err = new Error('Need to be logged in to view page');
                err.status = 403;
                return next(err);
    }
}

My thought process is that the profile page is only visable if a user is logged in, thus why we are checking if a userId object exists. The about page is still visible on any state and the 403 (forbidden) error checks for authorization of a user.

Is this a viable approach?

Thanks for your time!