I m currently working on a project to integrate Slide into our portal asGreat. I an interested in exploring and/or exchanging deliverable codes for this integration:
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
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]
