Home/ Questions/Q 773581
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T18:59:17+00:00

I have an application that integrates with Facebook using Oauth 2. I can authorize

  • 0

I have an application that integrates with Facebook using Oauth 2.

I can authorize with FB and query their REST and Graph APIs perfectly well, but when I authorize an active browser session is created with FB. I can then log-out of my application just fine, but the session with FB persists, so if anyone else uses the browser they will see the previous users FB account (unless the previous user manually logs out of FB also).

The steps I take to authorize are:

  1. Call [LINK: graph.facebook.com/oauth/authorize?client_id…]

This step opens a Facebook login/connect window if the user’s browser doesn’t already have an active FB session. Once they log-in to facebook they redirect to my site with a code I can exchange for an oauth token.

  1. Call [LINK: graph.facebook.com/oauth/access_token?client_id..] with the code from (1)

Now I have an Oauth Token, and the user’s browser is logged into my site, and into FB.

  1. I call a bunch of APIs to do stuff: i.e. [LINK: graph.facebook.com/me?access_token=..]

Lets say my user wants to log out of my site. The FB terms and conditions demand that I perform Single Sign Off, so when the user logs out of my site, they also are logged out of Facebook. There are arguments that this is a bit daft, but I’m happy to comply if there is any way of actually achieving that.

I have seen suggestions that:

A. I use the Javascript API to logout: FB.Connect.logout(). Well I tried using that, but it didn’t work, and I’m not sure exactly how it could, as I don’t use the Javascript API in any way on my site. The session isn’t maintained or created by the Javascript API so I’m not sure how it’s supposed to expire it either.

B. Use [LINK: facebook.com/logout.php]. This was suggested by an admin in the Facebook forums some time ago. The example given related to the old way of getting FB sessions (non-oauth) so I don’t think I can apply it in my case.

C. Use the old REST api expireSession or revokeAuthorization. I tried both of these and while they do expire the Oauth token they don’t invalidate the session that the browser is currently using so it has no effect, the user is not logged out of Facebook.

I’m really at a bit of a loose end, the Facebook documentation is patchy, ambiguous and pretty poor. The support on the forums is non-existant, at the moment I can’t even log in to the facebook forum, and aside from that, their own FB Connect integration doesn’t even work on the forum itself. Doesn’t inspire much confidence.

Ta for any help you can offer.
Derek

ps. Had to change HTTPS to LINK, not enough karma to post links which is probably fair enough.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I was having the same problem. I also login using oauth (I am using RubyOnRails), but for logout, I do it with JavaScript using a link like this:

    <a href="/logout" onclick="FB.logout();">Logout</a>

    This first calls the onclick function and performs a logout on facebook, and then the normal /logout function of my site is called.

    Though I would prefer a serverside solution as well, but at least it does what I want, it logs me out on both sites.

    I am also quite new to the Facebook integration stuff and played around the first time with it, but my general feeling is that the documentation is pretty spread all over the place with lots of outdated stuff.

    • 0