<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I think this would be great!<br>
Having this meta-tool will allow us to move one level up from the
current explicit client binding, making the LL Viewer (or any other of
the kind) one component among many others, while the main control of
the client side moves up... for us to experiment with. I don't see any
obstacle to making this meta-tool work for all platforms.<br>
+1000.<br>
<br>
Crista<br>
<br>
Stefan Andersson wrote:
<blockquote cite="mid:BLU134-W39730AB735563013788F7CD5AC0@phx.gbl"
type="cite">
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>Melanie,<br>
<br>
I wasn't suggesting the use of our client software, I was describing a
solution that has worked well for us. I believe that there are some
issues that simply can't be solved with an unhacked sl viewer, and this
would be a nice base to work around it.<br>
<br>
I actually forgot to add that it also offers to download the viewer and
install it, if it can't find any viewer present.<br>
<br>
Even so, given how small piece of code this launcher is, it would be
trivial to port to any environment.<br>
<br>
I guess I'm really suggesting that if any of this would make sense, we
would set up a forge project for a cross-platform viewer launcher
project, bsd licensed so it can be applied and repackaged as needed. We
would gladly contribute to such a project.<br>
<br>
Best regards,<br>
Stefan Andersson<br>
Tribal Media AB<br>
<br>
> Date: Wed, 25 Feb 2009 08:13:48 +0000<br>
> From: <a class="moz-txt-link-abbreviated" href="mailto:melanie@t-data.com">melanie@t-data.com</a><br>
> To: <a class="moz-txt-link-abbreviated" href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</a><br>
> Subject: Re: [Opensim-dev] User Authentication<br>
> <br>
> Hi,<br>
> <br>
> extra Client-Software may work well for Tribal, but who would want
<br>
> to maintain Windows, Linux and Mac versions of this?<br>
> I believe Tribal's launcher is Windows only, that makes it
somewhat <br>
> easier, but seeing that many devs are on Linux, locking out all <br>
> Linuxers like myself seems counterproductive.<br>
> <br>
> Melanie<br>
> <br>
> Stefan Andersson wrote:<br>
> > Dear colleagues;<br>
> > <br>
> > <br>
> > <br>
> > for some time now, we at Tribal Media have employed an
entirely different way of logging the viewer in, with tokens, that does
not constitute changing the viewer.<br>
> > <br>
> > <br>
> > <br>
> > What we do, is that we install a 'launcher' app on the users
computer. It serves a number of purposes:<br>
> > <br>
> > <br>
> > <br>
> > 1) Installs rezzme, genesis and osurl url monikers, all of
them taking tokens as auxiliary data - these monikers let people log
onto web sites, and launch a viewer with a pre-authenticated token by a
link. (see step 5)<br>
> > <br>
> > <br>
> > <br>
> > 2) Identifies installed viewers, and keep track of preferreed
viewer.<br>
> > <br>
> > <br>
> > <br>
> > 3) Provides a pre-login login form to do non-web pre-launch
authentication (in this case, this would probably be where the _form_
obtains the token to pass to step 5)<br>
> > <br>
> > <br>
> > <br>
> > 4) Launches pre-requisite software, as the TribalVoice.exe
for when voice should be enabled, or a Proxy to divert certain packets.<br>
> > <br>
> > <br>
> > <br>
> > 5) Launched preferred user, with seamless login (using the
login option of the ll viewer with dummy data to bypass the login
screen) supplying the TOKEN in a tweaked LOGINURI - an example of this
loginuri would be -loginuri <a class="moz-txt-link-freetext" href="http://">http://</a>{loginserver}/?token={token} - have
a look at the login service, it has been providing overloads and aux
data for some time now, just to be able to do this.<br>
> > <br>
> > <br>
> > <br>
> > 6) Provides for hypergrid cross-login by providing both
loginuri and target region as endpoint.<br>
> > <br>
> > <br>
> > While we might not want to provide all these options in
OpenSim, I think our approach has worked well for us and our clients.<br>
> > <br>
> > <br>
> > Most of the code for these options are actually already out
there in various scattered projects.<br>
> > <br>
> > <br>
> > Best regards,<br>
> > Stefan Andersson<br>
> > Tribal Media AB<br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > Date: Mon, 23 Feb 2009 14:31:25 -0800<br>
> > From: <a class="moz-txt-link-abbreviated" href="mailto:diva@metaverseink.com">diva@metaverseink.com</a><br>
> > To: <a class="moz-txt-link-abbreviated" href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</a><br>
> > Subject: Re: [Opensim-dev] User Authentication<br>
> > <br>
> > Right. The constraint here, let's not forget, is that we want
to continue to reuse the LL viewer for a while.<br>
> > I'm going to read that doc about OpenID tokens, but if it
requires participation from the viewer, forget it... We are and will
continue to be in LL Viewer hacking mode in the foreseeable future,
abnd I want to make things safe before a better viewer comes along.<br>
> > <br>
> > The bottom line question in my email, phrased in OpenID
terminology, is whether we can use the Viewer's IP address as the token.<br>
> > <br>
> > <br>
> > Tommi Laukkanen wrote: <br>
> > <br>
> > As we cannot change the viewer at the moment one could use
the opensim login code to create the token...<br>
> > <br>
> > regards,<br>
> > Tommi<br>
> > _______________________________________________<br>
> > Opensim-dev mailing list<br>
> > <a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
> > <a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
> > <br>
> > <br>
> > <br>
> > <br>
> >
------------------------------------------------------------------------<br>
> > <br>
> > _______________________________________________<br>
> > Opensim-dev mailing list<br>
> > <a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
> > <a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
> <a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Opensim-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>