[Tickets #10311] Re: Facebook authentication fails

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10311
------------------------------------------------------------------------------
  Ticket             | 10311
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Facebook authentication fails
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2011-07-14 23:33) wrote:

> Well, the last call is probably the UI refresh. There usually is  
> another call to sidebarUpdate, right after that.

Yeah, but the first (2) calls should come from Facebook, not from the  
horde prefs page.. e.g.,

127.0.0.1 localhost - [14/Jul/2011:19:18:15 -0400] "GET  
/horde/services/facebook?code=xxxx HTTP/1.1" 301 0 "-" "Mozilla/5.0  
(Macintosh; Intel Mac OS X 10.6; rv:5.0.1) Gecko/20100101 Firefox/5.0.1"
127.0.0.1 localhost - [14/Jul/2011:19:18:16 -0400] "GET  
/horde/services/facebook/?code=yyyy HTTP/1.1" 302 0 "-" "Mozilla/5.0  
(Macintosh; Intel Mac OS X 10.6; rv:5.0.1) Gecko/20100101 Firefox/5.0.1"
127.0.0.1 localhost - [14/Jul/2011:19:18:18 -0400] "GET  
/horde/services/prefs.php?app=horde&group=facebook HTTP/1.1" 200 15879  
"-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0.1)  
Gecko/20100101 Firefox/5.0.1"

> What I find strange is the double call to services/facebook, but I  
> guess it's Facebook trying to find a working URL?

No, that's expected. The authentication is a two step method. You will  
notice that the code returned in both calls is different. It's the  
final code that is considered the auth_token.