On Dec 6, 2006, at 9:46 AM, Brian Moseley wrote:
we've certainly talked a bit about it, altho we're not sure what it might mean yet. probably two things: 1) enabling cosmo to act as an openid server for other services - users would create cosmo accounts as normal and use their cosmo "principal url" as their openid url when registering with other services.
Part of the point of OpenID and related systems is to allow development of an ecosystem of identity providers. There are already a few of these, myopenid.net and (as of this week) technorati.com, and there will be more. I'm not sure that I see the value of Cosmo/ osaf.us becoming and identity provider. If we are looking at an out of the box scenario for Cosmo, you could make the argument for acting as an identity provider, but having a billion identity providers kind of defeats the purpose.
2) signing up for a cosmo account with an openid url rather than a username and password. #1 seems pretty straightforward, but we're not exactly sure what all the ramifications would be for #2.
I think that this is actually the highly desirable case, assuming continued adoption of OpenID and other ID systems, like Liberty/SAML, and assuming that we can figure out how this would integrate with our current user/account management functionality
it would be a a great intern project for sure.
If nothing else, we can advertise it as a Google Summer of Code project -- I'd be happy to mentor a project like that (and one for Chandler)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
