<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CKAN: Ticket #1611: Implement auth API calls for webstore/external use</title>
    <link>http://localhost/ticket/1611</link>
    <description>&lt;p&gt;
As part of &lt;a class="closed ticket" href="http://localhost/ticket/1574" title="enhancement: [super] Storage changes including automated save to Webstore (closed: fixed)"&gt;#1574&lt;/a&gt; we decided that it would be better for webstore (and future external services) to be able to authenticate simply with CKAN-Core.
&lt;/p&gt;
&lt;p&gt;
Currently webstore access the CKAN database to obtain the key for the user but it would be better if this connection was not so tightly bound and that webstore used an API as any other external service might.
&lt;/p&gt;
&lt;p&gt;
Need to discuss further with dread
&lt;/p&gt;
</description>
    <language>en-us</language>
    <image>
      <title>CKAN</title>
      <url>http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png</url>
      <link>http://localhost/ticket/1611</link>
    </image>
    <generator>Trac 0.12.3</generator>
    <item>
      
        <dc:creator>ross</dc:creator>

      <pubDate>Fri, 06 Jan 2012 10:49:47 GMT</pubDate>
      <title>status changed; resolution set</title>
      <link>http://localhost/ticket/1611#comment:1</link>
      <guid isPermaLink="false">http://localhost/ticket/1611#comment:1</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;new&lt;/em&gt; to &lt;em&gt;closed&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;resolution&lt;/strong&gt;
                set to &lt;em&gt;duplicate&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
See &lt;a class="assigned ticket" href="http://localhost/ticket/1550" title="enhancement: Allow simple auth via the API (assigned)"&gt;#1550&lt;/a&gt;
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>