Skip to content

Facebook Authentication FacebookTokenError: Error validating client secret, still logged in #1954

Open
@sudosean

Description

@sudosean
  • I understand that GitHub issues are not for tech support, but for questions specific to this generator, bug reports, and feature requests.
Item Version
generator-angular-fullstack x.x.x
Node 6.0.0
npm 3.8.9
Operating System OS X 10.10.5
Item Answer
Transpiler Babel
Markup HTML
CSS SCSS
Router ui-router
Build Tool Gulp
Client Tests Mocha
DB SQL
Auth Y

Hi,

I registered my app with facebook. I run gulp serve and start my application, click sign up, click log in with facebook. I am redirected, enter my email and password then am redirected to this error:

FacebookTokenError: Error validating client secret.
   at Strategy.parseErrorResponse (/Users/sea2574595/dev/Haystack-Development/node_modules/passport-facebook/lib/strategy.js:196:12)
   at Strategy.OAuth2Strategy._createOAuthError (/Users/sea2574595/dev/Haystack-Development/node_modules/passport-oauth2/lib/strategy.js:367:16)
   at /Users/sea2574595/dev/Haystack-Development/node_modules/passport-oauth2/lib/strategy.js:166:45
   at /Users/sea2574595/dev/Haystack-Development/node_modules/oauth/lib/oauth2.js:177:18
   at passBackControl (/Users/sea2574595/dev/Haystack-Development/node_modules/oauth/lib/oauth2.js:123:9)
   at IncomingMessage.<anonymous> (/Users/sea2574595/dev/Haystack-Development/node_modules/oauth/lib/oauth2.js:143:7)
   at emitNone (events.js:91:20)
   at IncomingMessage.emit (events.js:185:7)
   at endReadableNT (_stream_readable.js:926:12)
   at _combinedTickCallback (internal/process/next_tick.js:74:11)
   at process._tickCallback (internal/process/next_tick.js:98:9)

However if I return to the main page, I see in the console that I get logged in from the code that was provided from facebook:


<script>
  // This is called with the results from from FB.getLoginStatus().
  function statusChangeCallback(response) {
    console.log('statusChangeCallback');
    console.log(response);
    // The response object is returned with a status field that lets the
    // app know the current login status of the person.
    // Full docs on the response object can be found in the documentation
    // for FB.getLoginStatus().
    if (response.status === 'connected') {
      // Logged into your app and Facebook.
      testAPI();
    } else if (response.status === 'not_authorized') {
      // The person is logged into Facebook, but not your app.
      document.getElementById('status').innerHTML = 'Please log ' +
        'into this app.';
    } else {
      // The person is not logged into Facebook, so we're not sure if
      // they are logged into this app or not.
      document.getElementById('status').innerHTML = 'Please log ' +
        'into Facebook.';
    }
  }

  // This function is called when someone finishes with the Login
  // Button.  See the onlogin handler attached to it in the sample
  // code below.
  function checkLoginState() {
    FB.getLoginStatus(function(response) {
      statusChangeCallback(response);
    });
  }

  window.fbAsyncInit = function() {
  FB.init({
    appId      : '<my-app-id>',
    cookie     : true,  // enable cookies to allow the server to access 
                        // the session
    xfbml      : true,  // parse social plugins on this page
    version    : 'v2.5' // use graph api version 2.5
  });

  // Now that we've initialized the JavaScript SDK, we call 
  // FB.getLoginStatus().  This function gets the state of the
  // person visiting this page and can return one of three states to
  // the callback you provide.  They can be:
  //
  // 1. Logged into your app ('connected')
  // 2. Logged into Facebook, but not your app ('not_authorized')
  // 3. Not logged into Facebook and can't tell if they are logged into
  //    your app or not.
  //
  // These three cases are handled in the callback function.

  FB.getLoginStatus(function(response) {
    console.log('FACEBOOK LOGIN STATUS-------->', response);
    statusChangeCallback(response);
  });

  };

  // Load the SDK asynchronously
  (function(d, s, id) {
    var js, fjs = d.getElementsByTagName(s)[0];
    if (d.getElementById(id)) return;
    js = d.createElement(s); js.id = id;
    js.src = "//connect.facebook.net/en_US/sdk.js";
    fjs.parentNode.insertBefore(js, fjs);
  }(document, 'script', 'facebook-jssdk'));

  // Here we run a very simple test of the Graph API after login is
  // successful.  See statusChangeCallback() for when this call is made.
  function testAPI() {
    console.log('Welcome!  Fetching your information.... ');
    FB.api('/me', function(response) {
      console.log('Successful login for: ' + response.name);
      document.getElementById('status').innerHTML =
        'Thanks for logging in, ' + response.name + '!';
    });
  }
</script>

The nav bar provided by the yoeman generator (where it says, 'hi, test user') does not acknowledge that I am signed in though, and when looking in the sqlite db I do not see that any information was saved.
I can still create a user and/or login at that point as well.
Then only way for me to log out of facebook is to delete the cookies.

I provided the secret key that was given to me from facebook along with my app id in ALL the config/env files:

local.env.**.js:

FACEBOOK_ID: '<my-app-id>',
  FACEBOOK_SECRET: '<my-secret-key>',

Does anyone know where this issue may be coming from? I am a bit lost.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions