<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
All,<br>
<br>
Today we launched our OpenAuth service (<a class="moz-txt-link-freetext" href="http://dev.aol.com/openauth">http://dev.aol.com/openauth</a>) to
support some of our initiatives; the current tie-in to OpenID at this
point is just that our OP is built on top of our OpenAuth API. And of
course we're very interested in seeing how some of these types of
capabilities can be supported by standard protocols as well.<br>
<br>
Praveen's blog (<a class="moz-txt-link-freetext" href="http://dev.aol.com/blog/82">http://dev.aol.com/blog/82</a>):<br>
<blockquote type="cite">
<h1 class="title">AOL Launches Open Authentication (OpenAuth) Service</h1>
<!-- begin content --><!--<span class="taxonomy"></span>-->
<div class="content">
<p>After
many months of work, we've finally posted the documentation for AOL's
Open Authentication APIs at dev.aol.com/openauth! This is an exciting
day for the authentication development team, but even more exciting for
us as a company because it further proves the company's commitment to
open protocols. </p>
<p>On the development front we've very proud of the new APIs and the
interesting applications they make possible. Yes there are other "open"
APIs out there. But we think we've got an innovative approach that
isn't matched elsewhere. With AOL Open Authentication, a user can be
authenticated and an authentication token returned to a site or AJAX
application. What's interesting is that the application can then
interact with other AOL services on behalf of the user. If the user
hasn't given permission (granted consent) to that 3rd party, an
exception is returned and a URL can be loaded that prompts the user for
said consent. </p>
<p>We'll probably get some questions about why we invented another
proprietary, albeit open, authentication protocol. Especially since we
recently announced support for OpenId. Does AOL Open Authentication
mean we're not committed to OpenId? The answer to that is an emphatic
No! It does NOT mean we're backing off from our OpenId position. In
fact, our goal is to use open protocols whenever possible, and being
fans of OpenId that's our preference. But OpenId does not currently
support the breadth of use cases we must support, particularly service
invocation or consent management. That said, we are working on a
prototype extension to OpenId intended to cover some of those
additional use cases. </p>
<p>On the company front, we're very happy because we think these
APIs,
and others in the pipeline, cement AOL's commitment to being "open" and
providing APIs for different services. The internal buzz we hear from
our developer kin in other groups about providing APIs to different
services and AOL's growing involvement with developer communities is
starting to give us some great momentum, as we continue to build on our
new strategy. And that's great news to us.</p>
</div>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<br>
<a href="http://feeds.feedburner.com/aol/SzHO"><img
src="cid:part1.06000501.03070609@aol.net"
style="border: 0pt none ; float: right;" alt="Abstractioneer"></a>John
Panzer<br>
System Architect<br>
<a class="moz-txt-link-freetext" href="http://abstractioneer.org">http://abstractioneer.org</a><br>
</div>
</body>
</html>