<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 21 May 2013 20:39:54 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Wez Furlong's Blog: Identity/Authentication and PHP OpenSSL updates in the pipeline]]></title>
      <guid>http://www.phpdeveloper.org/news/6587</guid>
      <link>http://www.phpdeveloper.org/news/6587</link>
      <description><![CDATA[<p>
In his <a href="http://netevil.org/node.php?nid=924">latest post</a>, <i>Wez Furlong</i> shares some of the updates he's made to his blog - specifically when it comes to the external user authentication system he's implemented.
</p>
<blockquote>
Why do I have an external authentication mechanism? I don't want to maintain a user database just for my blog. It's more moving parts and requires things like sending email pings to random email addresses and mechanisms for resetting or retrieving a forgotten password. Not to mention that it's yet another username/password to be remembered by the person doing the commenting.
</blockquote>
<p>
So, instead, he authenticates against the php.net cvs setup for any and all users of his site. He transitions from this over to the main point of the post - his <a href="http://netevil.org/node.php?nid=924">thoughts on authentication</a>, specifically the move towards a more centralized resource to bounce the user's information off of. He mentions <a href="http://www.sixapart.com/typekey/">TypeKey</a> and <a href="http://openid.net/">OpenID</a> as two technologies that are moving in the right direction.
</p>
<p>
Bringing it back to PHP, <i>Wez</i> notes that the PHP support for both of these technologies is very lacking, but he's been working on a patch for the openssl extension that could help that significantly.
</p>]]></description>
      <pubDate>Thu, 26 Oct 2006 13:27:50 -0500</pubDate>
    </item>
  </channel>
</rss>
