Do not use hardcoded secret for OAuth2 providers

Docs > コード分析 > Static Analysis Rules > Do not use hardcoded secret for OAuth2 providers

このページは日本語には対応しておりません。随時翻訳に取り組んでいます。翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。

Metadata

ID: javascript-node-security/oauth2-hardcoded-secret

Language: JavaScript

Severity: Warning

Category: Security

CWE: 798

Description

Do not put hardcoded credentials in code. Instead, put secrets in environment variables or a vault.

Non-Compliant Code Examples

passport.use(new OAuth2Strategy({
    authorizationURL: 'https://www.example.com/oauth2/authorize',
    tokenURL: 'https://www.example.com/oauth2/token',
    clientID: `client_id`,
    clientSecret: 'secret_id',
    callbackURL: "http://localhost:3000/auth/example/callback"
  },
  function(accessToken, refreshToken, profile, cb) {
    User.findOrCreate({ exampleId: profile.id }, function (err, user) {
      return cb(err, user);
    });
  }
));

Compliant Code Examples

passport.use(new OAuth2Strategy({
    authorizationURL: 'https://www.example.com/oauth2/authorize',
    tokenURL: 'https://www.example.com/oauth2/token',
    clientID: process.env.EXAMPLE_CLIENT_ID,
    clientSecret: process.env.EXAMPLE_CLIENT_SECRET,
    callbackURL: "http://localhost:3000/auth/example/callback"
  },
  function(accessToken, refreshToken, profile, cb) {
    User.findOrCreate({ exampleId: profile.id }, function (err, user) {
      return cb(err, user);
    });
  }
));