Yes, I'd prefer Oauth too...It seems to me to fit better because it's service oriented...
On Wed, Jan 13, 2010 at 3:17 PM, Scott Wilson < [email protected]> wrote: > On 13 Jan 2010, at 14:54, Bernhard Hoisl wrote: > > Just a quick question if it is planned to integrate any sort of OpenID >> support in Wookie? Maybe with a call to the REST API before instantiating a >> widget? This would simulate a single-sign-on mechanism on a page where >> different Wookie widgets are displayed each needing authentication. >> >> I would need anything like that... >> >> -Bernhard >> > > Hi Bernhard, > > I hadn't thought of integrating OpenID in Wookie, however I would very much > like to have oAuth support in Wookie so that a Widget requiring access to a > remote service could request oAuth authorization by the user to the remote > service via Wookie in a similar manner to how Shindig supports this > capability. > > For authentication, Wookie assumes that applications authenticate users, as > this is how we assume concerns are separated - a single Wookie server can > support multiple applications, potentially in different organisations, and > so we do not implement authentication concerns. > > Maybe some use-cases could help articulate how an OpenID feature might > work? > > S > > -- http://www.hughbarnard.org http://www.big-wave-heuristics.com/ http://www.hackney-environment-network.org.uk/
