Reputation: 11
I hope my question doesnt sound stupid, But i really want to know this..
Is signed_request an alternative to access_code? If so, How do i receive the signed_request for desktop clients?
I mean flow that i follow in my desktop client is:
https://www.facebook.com/dialog/oauth?client_id=xxxx&redirect_uri=https://www.facebook.com/connect/login_success.html&response_type=token&scope=publish_stream
So will 1. and 2. be merged in a single request call to signed_request which says it will give the JSON object of user information in it.
How to make this call to get signed_request for desktop clients?
Upvotes: 1
Views: 607
Reputation: 4439
Two problems with your theory here:
In order to get a valid access_token within the signed_request, you'll still need to authenticate and request permission from a user, so in that case it's probably simpler to use the authentication flow fully rather than trying to parse the signed_request.
As stated in the Signed Request docs you will not receive any signed_request if you are building a desktop/device app.
Upvotes: 1