tracker issue : CF-3923044

select a category, or use search below
(searches all categories and all time range)
Title:

[ANeff] Bug for: <cfoauth type="facebook"> throws exception when endpoints specified

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/ThirdParty

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 01/19/2015

Components: Social

Versions: 11.0

Failure Type: Non Functioning

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Major / Some users will encounter

Locale/System: ALL / Platforms All

Vote Count: 0

The following throws exception "JSON parsing failure at character 1:'a' in access_token=access_token_here&expires=expires_here":

<cfoauth clientid="#clientID#" secretkey="#secretKey#" result="r" authendpoint="https://www.facebook.com/v2.2/dialog/oauth" accesstokenendpoint="https://graph.facebook.com/v2.2/oauth/access_token">

Facebook violates http://tools.ietf.org/html/rfc6749#section-5.1 by not returning JSON for this one call. However, <cfoauth> properly handles Facebook's bug when the endpoints aren't specified. So, <cfoauth> should also handle Facebook's bug when the endpoints are specified.

This issue makes <cfoauth> unusable if developer needs to specify Facebook's API version in the call.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3923044

External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:

Attachments:

Comments:

Adobe, I've filed this ticket w/ Facebook: https://developers.facebook.com/bugs/1535950696684684/ Facebook said: "We have managed to reproduce this issue and it appears to be a valid bug. We are assigning this to the appropriate team." Could this ticket here remain open until I follow-up w/ confirmation from Facebook that they've fixed the issue on their end? Thanks!, -Aaron
Comment by External U.
8960 | January 21, 2015 06:11:24 PM GMT
@Aaron Thanks for reporting the bug to facebook. Ticket will remain open and status will change to third party dependency.
Comment by Uday O.
8961 | January 22, 2015 03:28:46 AM GMT
Hi Uday, Thank you very much and you're welcome! Thanks!, -Aaron
Comment by External U.
8962 | January 22, 2015 04:08:07 AM GMT
Hi Uday, This ticket can be closed b/c Facebook's next API version will have the fix, per this comment from Facebook on that ticket: ----------- We have a fix this issue. In the next version of the API, which will probably be V2.3, this will be resolved. That means that from that moment on the access token returned will be in the JSON format. This is too big of a change to implement in the current version of the API (V2.2), so it will only be released in the next version. ----------- Thanks! -Aaron
Comment by External U.
8963 | January 27, 2015 06:11:51 AM GMT
Hi Uday, I've verified Facebook has fixed this in v2.3. The OAuth Access Token response is now valid JSON. The following works fine (I only changed 'v2.2' to 'v2.3'): <cfoauth clientid="#clientID#" secretkey="#secretKey#" result="r" authendpoint="https://www.facebook.com/v2.3/dialog/oauth" accesstokenendpoint="https://graph.facebook.com/v2.3/oauth/access_token"> <cfdump var="#r#"> This fix is documented in Facebook's v2.3 changelog: https://developers.facebook.com/docs/apps/changelog#v2_3 (just search that page for "Oauth Access Token"). Thanks!, -Aaron
Comment by External U.
8964 | April 30, 2015 11:48:20 AM GMT