We have the same situation: extended turbine's authentication/authorization
and have many Turbine applications ( all ecs based now ). What we did is
place all our applications inside the same zone and and have Jetspeed use
our auth extensions. This works pretty well for us right now.
But we now want to use templates ( WM/Velocity ) for our turbine
applications. I can't really see how to integrate jetspeed ( basically an
ECS/XML based turbine application ) and a templated application.
*) We want to maintain the common look and feel accross our applications
also. So using the user settings/prefs from jetspeed sounds great. Again
the integration is not clear to us yet.
Basically we want to use Jetspeed to allow our users:
*) to pull together information from all these different applications
*) arrange them how they want: layout
*) Set preferences, color, settings, etc.
*) Use what ever we want to develop the web application ( Turbine currently
). But also allow other web apps to appear on their portal page also.
There was talk a few months back on this list or the Turbine list, about
writing an external login server which multiple applications ( read: zones )
could use for authentication/authorization. Effectivly letting multiple
turbine apps share login information. It may get into sharing session
information accross zones and session failover also.
jb
-----Original Message-----
From: Diethelm Guallar, Gonzalo
To: 'JetSpeed'
Sent: 09/15/2000 8:36 PM
Subject: Putting another app on Jetspeed
Ok, here is the deal. I have developed a web app
using Turbine, and it has a user/permission system
(it actually extends Turbine's) to ensure each user
has access to his/her own stuff and nothing more.
What I would like to do is:
* Put something in Jetspeed that, once a user logs into
Jetspeed, will let them choose to go to a page with
links to all the stuff in my Turbine app that user can do.
Think "my app => a bank, what the user can do => browse
his accounts, credit cards, etc.".
* Pass the login information from Jetspeed to my Turbine
app, so that the user logs in only once.
* Embed my app in Jetspeed (I believe this is already
possible and pretty simple, right?).
What happens with things such as multiple Turbine jars
being loaded (one for Jetspeed, once for my App)? Should
I just redirect from Jetspeed to a separate "zone" (I'm
using Tomcat, but you get the idea)? If yes, how should
I share the login information so that the user logs in
only once on Jetspeed and is able to access all the
context in my Turbine app?
Am I making sense here?
Thanks,
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
------------------------------------------------------------------------
This message has been scanned for viruses with Trend Micro's Interscan VirusWall.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
