在Passportjs中刷新JWT令牌

时间:2019-04-30 15:59:33

标签: javascript passport.js openid-connect auth0 onelogin

我使用的是护照-openidconnect策略,效果很好,但是会话的有效期只有3600秒,我认为它是不会改变的。

我会使用刷新令牌来获取另一个令牌ID吗?

如果我这样做,该在哪里添加这种逻辑? https://github.com/passport/express-4.x-openidconnect-example/blob/master/server.js

1 个答案:

答案 0 :(得分:4)

会话的到期时间可以在auth提供者端进行配置。例如假设您使用auth0作为身份验证提供程序,则可以在应用设置(https://auth0.com/docs/tokens/guides/access-token/set-access-token-lifetime)上配置token超时

enter image description here

refresh token而言,护照本身不支持该护照,这取决于我们来实施。对于auth0,您可以按照https://auth0.com/docs/tokens/refresh-token/current上的流程更新令牌。我从该链接粘贴了代码:

var request = require("request");

var options = { method: 'POST',
  url: 'https://YOUR_DOMAIN/oauth/token',
  headers: { 'content-type': 'application/x-www-form-urlencoded' },
  form: 
   { grant_type: 'refresh_token',
     client_id: 'YOUR_CLIENT_ID',
     client_secret: 'YOUR_CLIENT_SECRET',
     refresh_token: 'YOUR_REFRESH_TOKEN' } };

request(options, function (error, response, body) {
  if (error) throw new Error(error);

  console.log(body);
});

或者您可以使用护照https://github.com/fiznool/passport-oauth2-refresh的附件

var passport = require('passport'),
  , refresh = require('passport-oauth2-refresh')
  , FacebookStrategy = require('passport-facebook').Strategy;

var strategy = new FacebookStrategy({
  clientID: FACEBOOK_APP_ID,
  clientSecret: FACEBOOK_APP_SECRET,
  callbackURL: "http://www.example.com/auth/facebook/callback"
},
function(accessToken, refreshToken, profile, done) {
  // Make sure you store the refreshToken somewhere!
  User.findOrCreate(..., function(err, user) {
    if (err) { return done(err); }
    done(null, user);
  });
});

passport.use(strategy);
refresh.use(strategy);

var refresh = require('passport-oauth2-refresh');
refresh.requestNewAccessToken('facebook', 'some_refresh_token', function(err, accessToken, refreshToken) {
  // You have a new access token, store it in the user object,
  // or use it to make a new request.
  // `refreshToken` may or may not exist, depending on the strategy you are using.
  // You probably don't need it anyway, as according to the OAuth 2.0 spec,
  // it should be the same as the initial refresh token.

});