facebook-csharp-sdk/facebook-csharp-sdk — Issue #60: Deprecation of Offline Access Permission
Author: ntotten
Created: 2012-02-06 19:33:01+00:00
State: open
Labels: Bug

With Facebook announcing the deprecation of Offline Access permission (https://developers.facebook.com/docs/offline-access-deprecation/), what is the right way to implement their guidance (below) on refreshing the access token using the FB C# SDK?
--

Client-side OAuth and Extending Access_Token Expiration Time through New Endpoint

Using the new endpoint below, you will be able to extend the expiration time of an existing, valid access_token. If the access_token was originally generated from a client-side OAuth call or through a signed_request, the endpoint will actually return a new access_token. You should use this new access_token going forward. The original access_token will continue to function until it expires, but again, it will be more effective to use the new access token with the longer expiration time.

To get the access_token or reset the expiration time for an existing access_token, simply pass your own client_id (your app_id), your app_secret, and the client-side access_token to the endpoint below. The returned access_token will be set to expire in 60 days.

https://graph.facebook.com/oauth/access_token?
client_id=APP_ID&
client_secret=APP_SECRET&
grant_type=fb_exchange_token&
fb_exchange_token=EXISTING_ACCESS_TOKEN