passport.js

问题 I am doing a react project using express and passport-local for the authentication part based on this tutorial : https://scotch.io/tutorials/easy-node-authentication-setup-and-local The authentification work very well, I added the express router to define my routes for my api, but when I call for example "/api/myroute" the router of express creates an other session and I lose the user, so my function isLoggedIn blocks the call of my controllers because there is no user in this new session. So

问题 I'm creating a SailsJS application, and I want users to log in only with Steam authentication. I used sails-generate-auth to create some boilerplate code with sails routes, but I'm having trouble plugging passport-steam into it. https://github.com/kasperisager/sails-generate-auth https://github.com/liamcurry/passport-steam The reported error is: C:\Users\Joe\testProject\node_modules\passport-steam\lib\passport-steam\strategy.js:67 id: result.response.players[0].steamid, ^ TypeError: Cannot

问题 Below is my server.js (app.js). I am using express with passport, for user authentication. But whenever I restart my node server user logsout. I am very new to nodejs, I was wondering how I could implement a cookie based authentication. So that user does not log out even if the server starts. I'm sure theres some config change which I have not able to find. // server.js // set up ====================================================================== // get all the tools we need var express =

问题 I'm using passport-jwt and my strategy is setup like: let jwtOptions = {} jwtOptions.jwtFromRequest = ExtractJwt.fromAuthHeaderAsBearerToken() jwtOptions.secretOrKey = process.env.SECRET var strategy = new JwtStrategy(jwtOptions, function (jwt_payload, next) { console.log('payload received', jwt_payload); // usually this would be a database call: var user = users[_.findIndex(users, { id: jwt_payload.id })]; if (user) { next(null, user); } else { next(null, false); } }) passport.use(strategy)

问题 After successfully logging in I am getting the jwt token, now to access restricted api's I am sending the authorization header, but I am always getting 401 Unauthorized I have referred to this Authenticating node API with passport-jwt question asked here but didn't helped me, this is the function I am calling for accessing data from resticted api check() { console.log(this.token); var headers = new Headers(); headers.append('Content-Type', 'application/json'); headers.append("Authorization",

问题 I'm new to passport and passport-saml , and I'm trying to build a Node.js server that uses our University's Shibboleth identity provider for single sign-on. I'm pretty close to getting it all working, but I'm hitting a snag during the /login/callback that I think is related to the encryption configuration. I am able to redirect the client to the sign-in page, and after a successful sign-in, the IdP does a POST back to my /login/callback route. Then I get this error: Error: Invalid signature

问题 Using Mongoose.js, my authenticate method populates the field "companyRoles._company," but the populated data reverts to the company reference ID when I try to access the same populated field in my req.user object. //Authentication UserSchema.static('authenticate', function(email, password, callback) { this.findOne({ email: email }) .populate('companyRoles._company', ['name', '_id']) .run(function(err, user) { if (err) { return callback(err); } if (!user) { return callback(null, false); }

问题 I'm using passport to authenticate users at my site. Users can register orders, which have and foreignKey (ObjectId) to the User object. Example-objects (written as mongoose schemas): var orderSchema = new mongoose.Schema({ ... address: String, _userID: {type: mongoose.Schema.Types.ObjectId, required: true, ref: 'User'} }); var userSchema = new mongoose.Schema({ email: String, }); Mongoose will create the primary key for each object. My question is; is it enough to check if req.user._id ===

问题 I built my own strategy for passport. Now an instance of my application runs behind a corporate firewall. Thus I need to get all outgoing requests passed to a proxy server first (http), which then connects to the outside world (https). I got this running with other modules like request which offer an option to pass a proxy config. `app -(http)-> proxy -(https via vpn tunnel)-> www`` Question 1) How can I force the outgoing requests from my passport strategy to go via the proxy? 2) If it is

问题 I built my own strategy for passport. Now an instance of my application runs behind a corporate firewall. Thus I need to get all outgoing requests passed to a proxy server first (http), which then connects to the outside world (https). I got this running with other modules like request which offer an option to pass a proxy config. `app -(http)-> proxy -(https via vpn tunnel)-> www`` Question 1) How can I force the outgoing requests from my passport strategy to go via the proxy? 2) If it is