[horde] Facebook

Michael J Rubinsky mrubinsk at horde.org
Mon Jul 2 15:05:29 UTC 2012


Quoting Rodrigo Abantes Antunes <rodrigoantunes at pelotas.ifsul.edu.br>:

> Http Client? There is no mention of this in the guide. Sorry, I  
> don't know much of oauth tokens and this process of authentication  
> with oauth tokens. I installed Horde_Oauth - Horde OAuth  
> client/server.

Do you have either the Pecl_Http extension or the PHP Curl extension  
installed?

>
> -- 
> Rodrigo Abrantes Antunes
> Técnico em Tecnologia da Informação
> Coordenadoria de Manutenção e Redes
> Instituto Federal Sul-rio-grandense - Campus Pelotas
>
>
>
> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>
>> Works fine here now.  Do you know what http client you are using on  
>> each server?
>> --
>> mike
>>
>> Sent from mobile
>>
>> Rodrigo Abantes Antunes <rodrigoantunes at pelotas.ifsul.edu.br> wrote:
>>
>> Quoting Rodrigo Abantes Antunes  
>> <rodrigoantunes at pelotas.ifsul.edu.br>> I updated Horde/OAuth and  
>> Horde/Service_Twitter but still the same
>>> problem. I mirrored this installation in another old server with  
>>> older php/apache versions and it worked, facebook also worked.
>>> -- 
>>> Rodrigo Abrantes Antunes
>>> Técnico em Tecnologia da Informação
>>> Coordenadoria de Manutenção e Redes
>>> Instituto Federal Sul-rio-grandense - Campus Pelotas
>>>
>>>
>>>
>>> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>>>
>>>> Quoting Rodrigo Abantes Antunes <rodrigoantunes at pelotas.ifsul.edu.br>:
>>>>
>>>>> I did some debug in code and It seems that no requestoken is  
>>>>> generated, in the file Oauth/Consumer.php the function  
>>>>> getRequestToken returns nothing.
>>>>>
>>>>> return Horde_Oauth_Token::fromString($response->getBody());
>>>>>
>>>>> An echo in $response->getBody() shows nothing and it should show  
>>>>> the oauth_token.
>>>>>
>>>>> Is there some class or extension that I may have missed? I  
>>>>> installed horde with "pear install -a -B horde/webmail".
>>>>
>>>> No, this was a combination of a number of issues. There was a bug  
>>>> in our OAuth code that caused the OAuth signature to be build  
>>>> incorrectly when communicating over SSL. There were also some  
>>>> minor changes in the Twitter API that necessitated changes to  
>>>> Service_Twitter as well as Horde.
>>>>
>>>> Both Horde/OAuth and Horde/Service_Twitter were fixed and  
>>>> released, the Horde changes will be available when the next bug  
>>>> fix release for the Horde package drops.
>>>>
>>>> -- 
>>>> mike
>>>>
>>>> The Horde Project (www.horde.org)
>>>> mrubinsk at horde.org
>>>
>>>
>>>
>>> -- 
>>> Horde mailing list
>>> Frequently Asked Questions: http://horde.org/faq/
>>> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>>>


-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6135 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.horde.org/archives/horde/attachments/20120702/c1a9b2d8/attachment.bin>


More information about the horde mailing list