[OpenID] AOL Open Authentication service launched

Recordon, David drecordon at verisign.com
Mon Apr 16 17:49:48 UTC 2007


Yes, this sounds great!  Looking forward to chatting with all of you at Web 2 Expo.

--David


 -----Original Message-----
From: 	Johannes Ernst [mailto:jernst+openid.net at netmesh.us]
Sent:	Monday, April 16, 2007 09:28 AM Pacific Standard Time
To:	OpenID General
Subject:	Re: [OpenID] AOL Open Authentication service launched

Yet another thing from AOL that will likely help move this market  
forward. Keep bringing it on, guys, this is great!

And please do feel free to assemble like-minded OpenID people to work  
on specs that you believe are needed beyond OpenID has today ;-)



Johannes Ernst
NetMesh Inc.

?? http://netmesh.info/jernst



On Apr 16, 2007, at 10:08, John Panzer wrote:

> All,
>
> Today we launched our OpenAuth service (http://dev.aol.com/ 
> openauth) 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.
>
> Praveen's blog (http://dev.aol.com/blog/82):
>> AOL Launches Open Authentication (OpenAuth) Service
>>
>> 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.
>>
>> 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.
>>
>> 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.
>>
>> 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.
>>
>
> -- 
>
> <SzHO.gif>
> John Panzer
> System Architect
> http://abstractioneer.org
> <SzHO.gif>
> _______________________________________________
> general mailing list
> general at openid.net
> http://openid.net/mailman/listinfo/general




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20070416/2cdf59a0/attachment-0001.htm>


More information about the general mailing list