<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>david rasch - making stuff work &#187; API</title>
	<atom:link href="http://www.davidrasch.com/tag/api/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.davidrasch.com</link>
	<description></description>
	<lastBuildDate>Mon, 04 Apr 2011 00:53:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>API Access to Users&#8217; Data</title>
		<link>http://www.davidrasch.com/2006/10/01/api-access-to-users-data/</link>
		<comments>http://www.davidrasch.com/2006/10/01/api-access-to-users-data/#comments</comments>
		<pubDate>Mon, 02 Oct 2006 03:06:18 +0000</pubDate>
		<dc:creator>drasch</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[rest]]></category>

		<guid isPermaLink="false">http://www.davidrasch.com/2006/10/01/api-access-to-users-data/</guid>
		<description><![CDATA[<p>Apparently our API discussion at PHP Appalachia struck quite a chord with Michael. </p> <p>As we&#8217;re in the process of building up the IntelliContact API, we&#8217;ve run into this same problem. We&#8217;ve taken a bit of a simple solution. We allow a given user to associate an API key with their account and specify <span style="color:#777"> . . . &#8594; Read More: <a href="http://www.davidrasch.com/2006/10/01/api-access-to-users-data/">API Access to Users&#8217; Data</a></span>]]></description>
			<content:encoded><![CDATA[<p>Apparently our API discussion at PHP Appalachia struck quite a <a href="http://fosterburgess.com/kimsal/?p=136">chord with Michael</a>.  </p>
<p>As we&#8217;re in the process of building up the IntelliContact API, we&#8217;ve run into this same problem.  We&#8217;ve taken a bit of a simple solution.  We allow a given user to associate an API key with their account and specify a separate password.  This allows the application using the API to access only users accounts to which they&#8217;ve been granted, and leaves the power with the user to revoke the access at will by changing the password or disabling the API key access entirely.  This seems to be a simple-end solution to what Michael proposes which allows for a more general ACL.</p>
<p>[tags]API, REST, authentication[/tags]</p>
]]></content:encoded>
			<wfw:commentRss>http://www.davidrasch.com/2006/10/01/api-access-to-users-data/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

