Terminating SGD Client by Web/URL?

Hi Patrick

Not sure if this is what you want but http://<your server>/examples/apis

shows the use of ITarantellaWebtopSession.endSession() to logout a user.

I've tried a few things with 'Simple Launchpad' and it appears to force

you to reauthenticate before allowing you to run another application.

Regards

Barrie

On 2005-08-17, Patrick <peichenberger@bs.wmc.ch> wrote:

> Hi Community

>

> With a lot of inventive efforts and of course your help we managed to get

> our Typo3/ND/Tarantella/Terminalserver-System in a LAN to work on a web

> basis. (Authorization against an ND in a Typo3-System, dynamically

> creating links to applications and appending the login data - hidden in a

> PHP-Session - to the URL on the server).

>

> But there is now a final crucial problem: When the user closes the

> application fetched by Tarantella, the SGD-Client still is connected. When

> an other user now logs in on the same workstation (in our Typo3/PHP-Portal

> and the ND) and clicks a link which opens an application using Tarantella,

> guess what happens: The mailbox - or whatever - of the formerly logged in

> is visible!

>

> So is there a possibility to terminate the former connection maybe by a

> link on the Typo3-Webpage, where the user is still logged in?

>

> (Sorry, it's extremely complex and hard to explain. So please ask me, if

> the question is not clear for you).

>

> Thanks a lot for your help

>

> Patrick

>

barrie at 2007-7-4 19:04:05 >

Hi Patrick

If there's anything we can do to provide more information or to redesign

something to make it easier to do what you want to do please let me

know. I can't promise anything but I will pass comments about your

experience on to product management.

Regards

Barrie

On 2005-08-18, patrick <peichenberger@bs.wmc.ch> wrote:

> Hi again Barry

>

> First of all: Thanks for your patience with us. This system design is

> really a horror and I'm sure we won't succeed with it despite of all

> efforts.

>

> Today we developed an application which bypasses the session mounting of

> Tarantella, and with these session information we are able to log out with

> another JSP-page without the SGD-Client.

>

> Thanks so far

>

> Patrick

>

>

> barrie wrote:

>

>> Hi Patrick

>

>> Not sure if this is what you want but http://<your server>/examples/apis

>> shows the use of ITarantellaWebtopSession.endSession() to logout a user.

>> I've tried a few things with 'Simple Launchpad' and it appears to force

>> you to reauthenticate before allowing you to run another application.

>

>> Regards

>>Barrie

>

>> On 2005-08-17, Patrick <peichenberger@bs.wmc.ch> wrote:

>> > Hi Community

>> >

>> > With a lot of inventive efforts and of course your help we managed to get

>> > our Typo3/ND/Tarantella/Terminalserver-System in a LAN to work on a web

>> > basis. (Authorization against an ND in a Typo3-System, dynamically

>> > creating links to applications and appending the login data - hidden in a

>> > PHP-Session - to the URL on the server).

>> >

>> > But there is now a final crucial problem: When the user closes the

>> > application fetched by Tarantella, the SGD-Client still is connected. When

>> > an other user now logs in on the same workstation (in our Typo3/PHP-Portal

>> > and the ND) and clicks a link which opens an application using Tarantella,

>> > guess what happens: The mailbox - or whatever - of the formerly logged in

>> > is visible!

>> >

>> > So is there a possibility to terminate the former connection maybe by a

>> > link on the Typo3-Webpage, where the user is still logged in?

>> >

>> > (Sorry, it's extremely complex and hard to explain. So please ask me, if

>> > the question is not clear for you).

>> >

>> > Thanks a lot for your help

>> >

>> > Patrick

>> >

>

>

>

barrie at 2007-7-4 19:04:05 >

On 2005-08-30, Ray <ray.schouten@acsdirect.com> wrote:

> Barrie. I'm taking advantage of your offer to consider and pass on

> suggestions for improvement.

>

> First, the ability to launch an app from a url is fantastic. But the

> implementation in TTA seems to be half baked. For instance, when

> initiating a url application launch, the user is required to pass the user

> name and password as components of the url string. This has the effect of

> passing the user name / password combination in the free text space,

> openly visible to the world. Really stupid for a company whose product

> key selling point is security.... (If this is wrong, please advise

> otherwise, but this is what we've gotten back on a support ticket reply).

>

It wasn't my understanding of how this worked. I'll do some

investigation and pass on what I've found. It is definitely not the way

it should work in the /sgd world. There was a workaround for this problem

in the old CGI (/tarantella) interface. Is it this that you need? If so,

I think you need to wrap './ttawebtop.cgi - ' in a perl script and use the POST

method feeding stdin of ttawebtop.cgi with the file to process.

Details hazy... I can get you more if you need them. I do remember it is

quite ugly, and tomcat makes this sort of thing much easier. I'll investigate

what you are supposed to do with the new client.

> The termination of the webtop initiated through the url launched

> applciation needs to initiate upon closeure/completion of the last running

> event involving the web-top. Suggest a delay timer to allow the

> administrator to configure a time delay from 0 - 8 hours (1 shift?) as a

> element of the object.

>

I think I understand what you are saying. I've half convinced myself

there is a workaround to this aswell. I'll try it out in some slack time and

let you know how I get on. Are you saying the webtop session should

terminate after a period of inactivity or when all applications are

suspended/ended?

> Other help suggestion. The ability to integrate the /tarantella and the

> new /sgd fractions of Tarantella lend themselves to customization

> (localization maybe). There is no asistance in this area to be found, and

> we can only glean bits of information making the cutomization a effort in

> frustration. A customization guide would VERY USEFUL!

>

Noted. You should be able to do everything using the new tomcat based

stuff. If there is something you think you need the cgi based stuff for

let me know. It's probably not a good idea to mix the two interfaces in a

single application, at least nobody knows what might occur if you do since

it never gets tested that way. I suspect you will end up logging out the

original session and starting a new one if you attempt this.

Localisation is definitely an issue.

> Many thanks in the most constructive of ways possible!

>

> Ray.

>

> barrie wrote:

>

>> Hi Patrick

>

>> If there's anything we can do to provide more information or to redesign

>> something to make it easier to do what you want to do please let me

>> know. I can't promise anything but I will pass comments about your

>> experience on to product management.

>

>> Regards

>>Barrie

>

>> On 2005-08-18, patrick <peichenberger@bs.wmc.ch> wrote:

>> > Hi again Barry

>> >

>> > First of all: Thanks for your patience with us. This system design is

>> > really a horror and I'm sure we won't succeed with it despite of all

>> > efforts.

>> >

>> > Today we developed an application which bypasses the session mounting of

>> > Tarantella, and with these session information we are able to log out with

>> > another JSP-page without the SGD-Client.

>> >

>> > Thanks so far

>> >

>> > Patrick

>> >

>> >

>> > barrie wrote:

>> >

>> >> Hi Patrick

>> >

>> >> Not sure if this is what you want but http://<your server>/examples/apis

>> >> shows the use of ITarantellaWebtopSession.endSession() to logout a user.

>> >> I've tried a few things with 'Simple Launchpad' and it appears to force

>> >> you to reauthenticate before allowing you to run another application.

>> >

>> >> Regards

>> >>Barrie

>> >

>> >> On 2005-08-17, Patrick <peichenberger@bs.wmc.ch> wrote:

>> >> > Hi Community

>> >> >

>> >> > With a lot of inventive efforts and of course your help we managed to

> get

>> >> > our Typo3/ND/Tarantella/Terminalserver-System in a LAN to work on a web

>> >> > basis. (Authorization against an ND in a Typo3-System, dynamically

>> >> > creating links to applications and appending the login data - hidden in

> a

>> >> > PHP-Session - to the URL on the server).

>> >> >

>> >> > But there is now a final crucial problem: When the user closes the

>> >> > application fetched by Tarantella, the SGD-Client still is connected.

> When

>> >> > an other user now logs in on the same workstation (in our

> Typo3/PHP-Portal

>> >> > and the ND) and clicks a link which opens an application using

> Tarantella,

>> >> > guess what happens: The mailbox - or whatever - of the formerly logged

> in

>> >> > is visible!

>> >> >

>> >> > So is there a possibility to terminate the former connection maybe by a

>> >> > link on the Typo3-Webpage, where the user is still logged in?

>> >> >

>> >> > (Sorry, it's extremely complex and hard to explain. So please ask me, if

>> >> > the question is not clear for you).

>> >> >

>> >> > Thanks a lot for your help

>> >> >

>> >> > Patrick

>> >> >

>> >

>> >

>> >

>

>

>

barrie at 2007-7-4 19:04:05 >