0
votes

We currently have many users with offline_access user tokens which we use to manage pages on their behalf. I have read the Removal of offline_access guide and the majority of the changes are clear, however there is one unknown we'd like to clarify.

Following the permanent deprecation of offline_access, we will switch to using non-expiring page access_tokens. We have thoroughly tested the workflow for new users, and have found no problems with exchanging short-lived tokens for long-lived ones, and then retrieving non-expiring page access_tokens using long-lived user access_tokens.

My query relates to retrieving non-expiring page tokens using existing offline_access access_tokens. The last sentence of 'Scenario 5: Page Access Tokens' in the aforementioned guide indicates that you should be able to use either long-lived access_tokens or offline_access access_tokens to retrieve non-expiring page access tokens, however when we tested with the offline_access tokens, the page access_tokens returned had a 2 month expiry date.

As the guide also states in Scenario 2 that offline_access tokens will only have their expiration date truncated to 60 days when the permission is permanently deprecated, we are making the assumption that at that point all offline_access tokens will be converted to long-lived user tokens.

If this assumption is correct, we have no problem as we already know page access_tokens obtained using long-lived user tokens have no expiry. However, if this assumption is incorrect and offline_access tokens will simply be given an expiry date at the point of deprecation, we have a problem as it seems that page access tokens retrieved with offline_access tokens will expire.

Is somebody able to confirm this assumption?

tl;dr When the offline_access permission is deprecated, will existing offline_access access_tokens be converted into long-lived user access_tokens, or will they just be given an expiry date?

1

1 Answers

0
votes

http://developers.facebook.com/roadmap/offline-access-removal/

Scenario 2: If you have been previously requesting offline_access - updated 4/30/2012

Once the migration has been enabled, existing use access_tokens, with the offline_access permission, will continue to work without any change to their expiration time. However, new users to your app will not be prompted for the offline_access permission in the Auth Dialog and will receive either a short-lived or long-lived access_token depending on your environment and how you are requesting the access_token (client or server-side OAuth, see Scenario 3 and 4 below).

After the offline_access removal date (see roadmap for exact date), all existing offline_access access_tokens will have their expiration time truncated to 60 days. This truncation will be transparent to the user and your app will continue functioning normally; Facebook will send an updated message through the weekly developer round-up when this truncation will occur.