--- Begin Message ---
Peter Anders�n wrote:
Hi
This sounds interesting do you need any assitance or testing.
I am still trying to put things together and figuring out the direction
of Slide 2. Working under official channels of current Slide 2 and
Jetspeed 2 (now the top level Apache portal) are preferred (both lists
have very highly qualified and professional people). I will jump in and
out of these discussions due to my very erratic time table.
As a start, i will set up this or next weekend facilities for this
integration project: a cvs repository, tomcat5 with HTTPS, mysql
database and slide 2.0 that uses JDBC store as its root and tx store for
portlets. We can share the issues in making Slide into a functional
content management. Any concrete solution can give back to Apache Slide
and portal projects.
It seems to me items in Slide proposals are the way active committers
are heading, e.g. wvcm api rather than the old slide api is more
appropriate. Also JAAS and a newly added tamino. It makes sense to me
that the security authentication must be done at Tomcat portal level
(per Servlet spec) and programmatically link to finer details of
authorization and/or further authentication challenge. As a side note,
tomcat 5 indicates that its manager application will also move to the
direction of web service. So portlet is the core piece that must be done
first in our integration game.
I am interested in exploring this area.
BaTien
DBGROUPS
Regards
Peter A
----- Original Message -----
From: "BaTien Duong" <[EMAIL PROTECTED]>
To: "Slide Users Mailing List" <[EMAIL PROTECTED]>
Sent: Friday, March 26, 2004 11:14 PM
Subject: Re: Portal integration with Slide
Chamberlain James O. CONTR J9C998 wrote:
I m currently working on a project to integrate Slide into our portal as
a JSR-168 compliant portlet. I have a first rev with minimal
functionality (browsing, uploading, deleting, and locking), but no acl
or versioning support. Today it is using the Slide client API which
forces it to know the user's username and password. I am uncomfortable
with this solution and feel that it will get shot down in my environment
because of this. What other options are available for integrating with
Slide where it can share the user's principal? Is using the Slide API
the right answer?
Any recommendations or ideas would be appreciated.
Regards,
James
Great. I an interested in exploring and/or exchanging deliverable codes
for this integration:
1) Tomcat 5 container-managed user authentication that fully
integrated with Slide 2.0 ACL authorization which uses database as its
root (/) store.
2) Slide management via JSR-168 portlet. It will be ideal if we can
integrate with Tomcat 5 manager in a single manager portlet.
3) Slide versioning and workspace configuration management.
We can do it via the list or off-list if it is offended to other users.
I think the Jetspeed committers also have interest in this integration.
BaTien
DBGROUPS
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
.
--- End Message ---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
