[Opensim-dev] OAuth as authentication and authorisation (capability) specification

[diva at metaverseink.com]

Right. It seems to me that some of these techniques that are being 
considered (and deployed) for the Web assume that the client is pretty 
dumb. So instead of hacking around it, maybe the Web needs a better 
client! :) Doesn't need to be as featureful as on-line game clients, but 
it could certainly use some of the ideas that we're experimenting with 
here. And while I understand the desire for OpenSim to stay in sync with 
the Web, I think it's a shame if we don't take advantage of the 
opportunity to experiment with a different kind of web -- one where the 
concepts of users, application trust domains, and resource services are 
at the center.
That is what I saw, vaguely, in SL, and now very clearly in OpenSim.


Melvin Carvalho wrote:
> On Tue, Apr 28, 2009 at 1:34 PM, Tommi Laukkanen
> <tommi.s.e.laukkanen at gmail.com> wrote:
>> I think Diva's point was that when using rich client we can collect
>> the credentials with a dialog and post them to openid. On http level
>> we can do the same tricks but we don't need necessarily switch to web
>> browser but we can stay inside the viewer.
> 
> Not sure what you mean by "post to openid", since every openid
> provider is different, and generally will have different credentials,
> and a different input mechanism.  The expectation of OpenID is a
> browser redirect.  In the event that some services are standarized,
> and have an API, a rich client could indeed store credentials, and
> post them.  But it's not a guarantee that this will always be
> possible.
> 
>> -tommi
>> _______________________________________________
>> Opensim-dev mailing list
>> Opensim-dev at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
>