简体   繁体   English

一旦永久弃用该权限,带有offline_access的用户访问令牌将发生什么?

[英]What exactly will happen to user access tokens with offline_access once that permission is permanently deprecated?

We currently have many users with offline_access user tokens which we use to manage pages on their behalf. 当前,我们有许多具有offline_access用户令牌的用户,我们用来代表他们管理页面。 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. 我已经阅读了《 删除offline_access指南》,并且大部分更改都很清楚,但是我们想澄清一个未知的地方。

Following the permanent deprecation of offline_access, we will switch to using non-expiring page access_tokens. 永久弃用offline_access之后,我们将切换为使用未过期的页面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. 我们已经为新用户彻底测试了工作流程,没有发现将短期令牌替换为长期令牌,然后使用长期用户access_tokens检索未过期的页面access_tokens的问题。

My query relates to retrieving non-expiring page tokens using existing offline_access access_tokens. 我的查询与使用现有的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. 上述指南中的“方案5:页面访问令牌”的最后一句表明,您应该能够使用长期存在的access_tokens或offline_access access_tokens来检索未过期的页面访问令牌,但是,当我们使用offline_access令牌进行测试时,返回的页面access_tokens的有效期为2个月。

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. 正如该指南还在方案2中指出的那样,当永久弃用该许可权时,offline_access令牌的到期日期将仅被截断为60天,因此我们假设此时所有的offline_access令牌都将转换为长期用户令牌。

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. 如果这个假设是正确的,那么我们就不会有问题,因为我们已经知道使用寿命长的用户令牌获得的页面access_tokens不会过期。 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. 但是,如果这个假设不正确,并且在弃用时将给offline_access令牌一个简单的到期日期,我们就会遇到一个问题,因为用offline_access令牌检索的页面访问令牌似乎将过期。

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? tl; dr不赞成使用offline_access权限时,将现有的offline_access access_tokens转换为寿命长的用户access_tokens,还是将其赋予有效期?

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

Scenario 2: If you have been previously requesting offline_access - updated 4/30/2012 方案2:如果您以前曾请求过offline_access-更新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. 启用迁移后,具有offline_access权限的现有使用access_tokens将继续工作,而其到期时间没有任何变化。 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). 但是,您的应用程序的新用户将不会在“身份验证”对话框中提示获得offline_access权限,并且会收到短期或长期的access_token,具体取决于您的环境以及您请求access_token的方式(客户端或服务器端OAuth ,请参见下面的方案3和4)。

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. 在offline_access删除日期(确切的日期,请参阅路线图)之后,所有现有的offline_access access_token的到期时间都将被截断为60天。 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. 截断发生时,Facebook将通过每周的开发人员摘要发送更新的消息。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM