I am in the process of reading all documents related to native desktop programming programming for Facebook. I clearly state the native desktop app, it will use client side authentication without Java SDK.
As far as I've read, I know that access_tokens are ending. I have also read that you can re-certify. But ........... Facebook has very limited documentation that how to run with desktop application without Java ADK, using client-side authentication on Windows / Mac OSX or Linux.
My question is ... Is this possible for such a Facebook desktop app or do I have to allow user to authorize my application after the expiry time of access_token Ask for
Important note : Facebook found solution Yes, it is possible to re-authenticate for the native desktop client is. Access_token (Users provided by Facebook during AP authentication) make connections between Facebook and my desktop app. This access_token (a string of 111 tokens) is valid for 60 days. The user must authenticate when it is finished, but there is no need to re-mark all options to specify permissions in my original desktop app. This happens when a user logs in to Facebook Again, without any other action (only the right URL entered with the correct scope of permissions With a login). The user of my desktop app is then sent to the URL that only shows success messages. So you need a browser or you need to get the HTTP and post the request by the code yourself. offline_access does not support permission function / API. (What could be the solution now).
https://www.facebook.com/dialog/oauth?client_id=YourAppClientIDGivenByFacebookDuringAppRegistration&redirect_uri = Https: //www.facebook.com/connect/login_success.html&scope=PermissionsScope
Comments
Post a Comment