<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>OAuth consumer support</title> 
  <pubDate>Thu, 09 Apr 2026 18:03:13 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7147</link> 
  <atom:link rel="self" type="application/rss+xml" title="OAuth consumer support" href="https://bugs.horde.org/ticket/7147/rss" /> 
  <description>OAuth consumer support</description> 
 
   
   
  <item> 
   <title>We have the necessary client code for this in the Horde_Oaut</title> 
   <description>We have the necessary client code for this in the Horde_Oauth package. What we need is a preferences container for OAuth credentials and some scripts (probably in horde/services/) for callbacks and setting up OAuth tokens to various providers that we might want to access on behalf of Horde users.</description> 
   <pubDate>Sun, 03 Aug 2008 01:47:49 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7147#t47964</link> 
  </item> 
   
  <item> 
   <title>If other code is needed for interfacing with e.g. twitter:
</title> 
   <description>If other code is needed for interfacing with e.g. twitter:
http://github.com/abraham/twitteroauth</description> 
   <pubDate>Fri, 17 Sep 2010 03:39:35 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7147#t60051</link> 
  </item> 
   
  <item> 
   <title>FWIW, Horde_Service_Twitter has worked with OAuth (via our H</title> 
   <description>FWIW, Horde_Service_Twitter has worked with OAuth (via our Horde_OAuth library) from the beginning...</description> 
   <pubDate>Fri, 17 Sep 2010 16:55:51 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7147#t60054</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
