JFBC - Open Auth?

I got an angry email from Facebook! Apparently something on my site's not using OAuth to communicate with Facebook.

I'm pretty sure JFBC 3.0.3 does but can someone please confirm this so I can whittle down the offending extension.

Many thanks.

Thanks so much for the quick response, Alex - much appreciated. So, to clarify, does 3.2 use the latest OAuth that Facebook requires?

Thanks, Ricky

FYI, the FB email says:

Our automated systems have detected that you may be inadvertently allowing authentication data to be passed to 3rd parties. Allowing user ids and access tokens to be passed to 3rd parties, even inadvertently, could allow these 3rd parties to access the data the user made available to your site. This violates our policies and undermines user trust in your site and Facebook Platform.

In every case that we have examined, this information is passed via the HTTP Referer Header by the user's browser. This can happen when using our legacy authentication system and including <iframe>, <img> or <script> content from 3rd parties in the page that receives authentication data from Facebook. Our legacy mechanism passes authentication information in the URL query string which, if handled incorrectly, can be passed to 3rd parties by the browser. Our current OAuth 2.0 authentication system, released over a year ago, passes this information in the URL fragment, which is not passed to 3rd parties by the browser.

Please ensure that you are not allowing this data to be passed immediately. Accessing your site as a test user while running a HTTP proxy/monitor like Charles or Fiddler is the best way to determine if you are allowing this information to be passed. If you discover the issue, you can do one of two things:

1. Migrate your site to use our OAuth 2.0 authentication system. We are requiring all apps and sites to update to this mechanism by Sept. 1, 2011. Migrating now will address this issue and ensure that you are one of the first to meet the deadline. For more details, please see our Authentication Guide.

2. Create and use an interstitial page to remove the authentication data before redirecting to your page with 3rd party content. This approach is used by many of our largest developers today (although they are all migrating to OAuth 2.0 shortly). This is a simple and straightforwardchange that should have minimal impact on your site. For more details on this approach, see our Legacy Connect Auth doc.

Because of the importance of ensuring user trust and privacy, we are asking you to complete one of the above steps in the next 48 hours. If you fail to do so, your site may be subject to one of the enforcement actions outlined in our policies.

If you have any questions or believe you have received this message in error, please contact us.

Facebook Developer Relations

Thanks Alex,

I'll buy the latest version of JFBConnect - hopefully that will work.

I've got other extensions that use Facebook, but they're just the 'like' and 'share' ones which, as you say, don't use OAuth as far as I know.

Best,

Ricky

I also just got the same email from Facebook. I am currently running JFBConnect 3.1.2 and will be upgrading to the latest version. The only other extension that I am using is Fan Box. Any other suggestions on what I should look for? The email states the problem needs to be resolved in 48 hours.

Hi Alex,

I just sent you a PM. I had just completed upgrading to 3.2.1 when you posted your reply. I am now experiencing a couple of other issues after the upgrade. I gave you the details in the PM.

Thank you for your help.

Mike

Hi Alex,

Yes, I got another email today about OAuth 2.0 so I'll wait for your update ASAP.

To clarify also, when I update to the new version, I won't have to reset my config data etc, will I?

Thanks!