"/auth/linkedin" Does not redirect to linkedin.

[collinglass]

My config has linkedin enabled like so:

{
linkedin: {
            enabled: true,
            auth: function(token, tokenSecret, profile, done) {...},
            client_id: "fooooooo",
            client_secret: "ba@@ar",
            scope: ["foo", "bar", "r_fullprofile"]
        }
}

My linkedin account also has the correct port for callback. My same setup was not changed from a working version with express.
After diving into your code, I found a couple differences:

1. passport-linkedin was not working for me, I used https://github.com/auth0/passport-linkedin-oauth2. It has been updated more recently.
2. On my route "/auth/linkedin" I had to update it to passport.authenticate( "linkedin", { state: 'some state' } ) ); This is found on Line 443 in your code (however it still didn't work when I changed it.)
3. Also, in my express code I had to add passReqToCallback: true to my passport options so I could add the token to the session store.

This could very well be my own error, so if it is not an error, and you in fact are able to get redirected, maybe I could be pointed in the right direction.

[avoidwork]

I'm just going to guess you where you using 'localhost' which is rewritten to 127.0.0.1, which means your cookie is lost. LinkedIn auth has been stable for 3 minor releases.

[collinglass]

I had 127.0.0.1 set, I'm sure I was doing something wrong. Any chance on getting a linkedin tutorial out on http://avoidwork.github.io/tenso/tutorials.html anytime soon?

[avoidwork]

Yeah, sure... but it'll be pretty basic. You're only filling out the config and not setting the routes right? They're generated for you.

[collinglass]

I wrote the above in my config (with correct client and scope data) and it didn't redirect, it just waited..

My complete config:

var config = {
    routes: routes,
    hostname: "127.0.0.1",
    port: 1337,
    auth: {
        protect: ["/something"],
        bearer: {
            enabled: true,
            tokens: []
        },
        linkedin: {
            enabled: true,
            auth: function(token, tokenSecret, profile, done) {
                users.linkedin(token, profile).then(function(result) {
                    done(null, result);
                });
            },
            client_id: "...",
            client_secret: "...",
            scope: ['r_network', 'rw_groups', 'r_fullprofile']
        }
    },
    headers: {
    }
}

[avoidwork]

I'll test that tonight, but it's practically the same as my tests. I do see you not handling the error case of your promise tsk tsk ;)

[avoidwork]

The combo of bearer + linkedin is not playing nice.

[avoidwork]

Bearer auth is currently not tied to an end point, so when you try to access the first step of the linkedin auth, you're already technically unauthorized via the session, hence the message. Bearer & Basic will have to be tied to new /auth end points.