I\'m building an application with the following blocks:
Android - Client Side, Java Servlets - Sever Side, Facebook app - used in order to authenicate users and wo
The better answer to this question (incorporating info from tomas.tunkl's comment) is as follows:
(Since I linked the documentation, I'm also going to put a bit of info from that debugging-and-error-handling link in here to show how to make the call and what you get back:)
When working with an access token, you may need to check what information is associated with it, such as its user or expiry. To get this information you can use our debug tool, or you can use the API endpoint.
To use the API, you can issue a Graph API request:
GET /debug_token? input_token={input-token}& access_token={access-token}
input_token: the access token you want to get information about
access_token: your app access token or a valid user access token from a developer of the app The response of the API call is a JSON array containing a map of fields. For example:
{ "data": { "app_id": 000000000000000, "application": "Social Cafe", "expires_at": 1352419328, "is_valid": true, "issued_at": 1347235328, "scopes": [ "email", "publish_actions" ], "user_id": 1207059 } }
Note that the issued_at field is not returned for short-lived access tokens.
This will ensure that you have a valid token for a facebook user that has been generated from your own secret key for a user; meaning that they have authenticated properly.
So you have: Facebook - Android Application - Your web server. And your web server needs to know that you are the Facebook user you are presenting. The problem is that you can not trust the Android client for any data it gives to you.
I solved the problem like this:
If the debug endpoint API call from your web server returns valid information (app id & user id), your server can trust the id (& you can be sure that the Android authentication is real)