Christian Scholz wrote:
> What exactly is the ID server? And if you have some sort of server then
> I guess it would be easy to write some web frontend to create some XRDS
> or XRD file, after all it's rather simple XML. (Some OpenID or XRI
> providers even let you edit your XRDS file already).
Diva Canto schrieb:
> Christian Scholz wrote:
>> We have been talking about it quite a bit in early 2008 in the
>> DataPortability Group. There was also some discussion about that concept
>> in the DiSo group.
>>
>> [...]
>
> Cool.
>
>>> Point 4 is also pretty much covered, with code already in
I forgot something to add.
Diva Canto schrieb:
> So far, I haven't felt the need for OpenID whatsoever. Login can be
> performed directly with the User Server, it doesn't need to be
> redirected from anywhere. (I have a problem with those redirections,
> they are utterly unsafe; if they can be
Christian Scholz wrote:
> We have been talking about it quite a bit in early 2008 in the
> DataPortability Group. There was also some discussion about that concept
> in the DiSo group.
>
> [...]
Cool.
>> Point 4 is also pretty much covered, with code already in place in
>> OpenSim, used by G
Diva Canto schrieb:
> That sounds reasonable. I should find out more about what the Web 2.0
> crowd is thinking for the "service catalogue", haven't heard that before
> coming from them. Because that's exactly where I have been taking OpenSim :)
We have been talking about it quite a bit in early
That sounds reasonable. I should find out more about what the Web 2.0
crowd is thinking for the "service catalogue", haven't heard that before
coming from them. Because that's exactly where I have been taking OpenSim :)
Point 4 is also pretty much covered, with code already in place in
OpenSim,
Diva Canto schrieb:
> Let's focus on the goal, before discussing techniques: "I would like to
> use my google identity in OpenSim as soon as possible :)"
>
> Once you've been ID'ed, where would your user services be?
For instance by using a service catalogue which is bound to your OpenID
and li
>From: Nebadon Izumi
>yes you will becasue with texture changer, unless your referencing UUIDS
>that are already uploaded, IE webloading images into your sim, even if its
>the same Image, everytime its fetched remotely it will be given a new UUID
>and decoded... so as you can see if your displayi
Charles Krinke schrieb:
> That is an interesting point. I think the perception by some is that we
> would like to have 'seamless' use of openid/oauth between various grids
> as folks might move from grid to grid using OGP, MXP, HG or other
> interop notions. So, popping up a password dialog in t
oh. it looks like the kind of problem that proxy certificates were
supposed to solve.
-Kyle H
On Fri, Apr 24, 2009 at 9:21 PM, Tommi Laukkanen
wrote:
> Hello
>
> OAuth seems to provide OpenSimulator server side authentication and
> authorisation needs. If you are interested in this area please
Let's focus on the goal, before discussing techniques: "I would like to
use my google identity in OpenSim as soon as possible :)"
Once you've been ID'ed, where would your user services be?
Tommi Laukkanen wrote:
> Hello
>
> OAuth seems to provide OpenSimulator server side authentication and
>
That is an interesting point. I think the perception by some is that we would
like to have 'seamless' use of openid/oauth between various grids as folks
might move from grid to grid using OGP, MXP, HG or other interop notions. So,
popping up a password dialog in the midst of a teleport might be
Stefan,
i did play yesterday and today with different version over my whole set of
regions.
While I have to admit not to be looking for something perfect and errorfree
- SVN 9292 does look nice to me.
Anyone better suggestions ?
Somewhere in the later versions I have more trouble with region cr
On Sat, Apr 25, 2009 at 5:09 PM, Tommi Laukkanen
wrote:
> Hello
>
>>
>> Oauth is not an authentication system, it is delegated credentials
>> system via a third party.
>>
>
> Authentication and authorisation with delegated credentials is what we
> need as identities will be provided by identity pr
yes you will becasue with texture changer, unless your referencing UUIDS
that are already uploaded, IE webloading images into your sim, even if its
the same Image, everytime its fetched remotely it will be given a new UUID
and decoded... so as you can see if your displaying the same few images over
At 11:02 25/04/2009, Nebadon Izumi wrote:
>the j2k cache files do have their own subfolder, but the files should be
>pretty tiny but for every texture in your region you will have the decoded
>information.. these are very necessary at this point. you can safely purge
>this folder every update and
Ccan someone remind me who did the scripts which built the nightly
binaries that were at http://builds.opensimulator.org/
And is there a plan to reactivate those? The last ones are dated
13-Apr-2009. Sorry if this has already been answered and I missed it
due to Easter travel.
__
Hello
>
> Oauth is not an authentication system, it is delegated credentials
> system via a third party.
>
Authentication and authorisation with delegated credentials is what we
need as identities will be provided by identity providers and assets
from asset providers in distributed model. We need
On Sat, Apr 25, 2009 at 6:21 AM, Tommi Laukkanen
wrote:
> Hello
>
> OAuth seems to provide OpenSimulator server side authentication and
> authorisation needs. If you are interested in this area please read
> this page and especially the "What is it for"-chapter:
Oauth is not an authentication sys
Hello
Yeah I noticed it before posting and I see it as a living evidence
that the community is credible and they take security holes seriously.
As far as I understood it seemed to be related to usage of oauth from
web browser and some careless accepting of rights by the user. Similar
to some openi
> As you can see from the wiki front page for example google offers
> standard oauth api. I would like to use my google identity in OpenSim
> as soon as possible :).
Maybe you should still wait a bit: http://oauth.net/advisories/2009-1
If I interpret this correctly, the current OAuth specification
21 matches
Mail list logo
