title: Is "profile" scope required for Google OAuth2.0?
body: <p>I'm currently trying to allow users of my application to authorize my app to access their Doubleclick for Advertisers API. I'm handling this authorization using <a href="http://passportjs.org/" rel="nofollow">Passport.js</a>. When I include both the <a href="https://developers.google.com/+/api/oauth#login-scopes" rel="nofollow">profile scope</a> and DFA scope like this:</p>
  
  <pre><code>  app.get '/requestAccess', passport.authenticate 'dfa',
      scope: [
        'https://www.googleapis.com/auth/dfatrafficking',
        'profile'
      ]
  </code></pre>
  
  <p>This works fine. However, I only care about the DFA api, and I don't actually intend on using anything from the profile scope, so I'd like to remove that:</p>
  
  <pre><code>  app.get '/requestAccess', passport.authenticate 'dfa',
      scope: [
        'https://www.googleapis.com/auth/dfatrafficking',
      ]
  </code></pre>
  
  <p>When I authorize using this route now, I get:</p>
  
  <pre><code> "error": {
    "errors": [
     {
      "domain": "global",
      "reason": "insufficientPermissions",
      "message": "Insufficient Permission"
     }
    ],
    "code": 403,
    "message": "Insufficient Permission"
   }
  }
  </code></pre>
  
  <p>Which comes from Google, meaning that the scope I requested with was insufficient. Is the profile scope required then for any kind of additional access? Why can't I only request the DFA scope?</p>