twitter / google plus - me request Not Found response?

[Gerst20051]

I keep getting Not Found for the me request from twitter and google plus. how should i load user data after getting the token via server side through twitter and google plus? Facebook is working perfectly...

[kalanbates]

@Gerst20051 Were you able to validate your google plus provider inside the oauthd portal with a "Try auth" request?

I can't get the popup to load google's auth gateway page.

[Gerst20051]

@kalanbates I'll let you know soon but I think it's fixed now!

[kalanbates]

@Gerst20051 I'm thinking the same thing. I ran across this issue report while I was investigating an issue I was having setting up google_plus as an oauth provider in my daemon. Come to find out, the problem I was having testing the provider was due to a corporate network policy designed to keep employees out of gmail...they blacklisted accounts.google.com, but the daemon was not exposing the tunnel connection error to my dev tools. It just kept failing the "Try Auth" test.

Once I figured this out, I switched connections to an unencumbered network and the Try Auth passed.

The odd thing that I'm currently experiencing is that when calling accessToken.me() for a google token, I receive the following response

{
   gender: 1,
   raw: {
      error: {
         code: 403,
         errors: [ ...],
         message: "Access Not Configured. The API is not enabled for your project, or there is a per-IP or per-Referer restriction configured on your API key and the request does not match these restrictions. Please use the Google Developers Console to update your configuration."
      }
   }
}

...the odd part is that I configured (assuming no typos) my Google Auth App identically to my Facebook Auth App, so I'm unsure why the behavior is different.

At any rate,

var getUserProfile = function(accessToken){
        var deferred = $q.defer();
        accessToken.me()
            .done(function(response){
                console.log(response);
                deferred.resolve(response);
            })
            .fail(function(error){

                console.log("An Error occurred retrieving user profile information");
                console.log("Error:" + error);
                deferred.reject(new Error("[Service|GetUserProfile] Failed"));
            });             
        return deferred.promise;
    }

works like a champ at retrieving profile info from the authentication system.