Sumit Ranjan wrote:
> jetspeed requires a user to authenticate himself.
> if i put some of my intranet applications as jetspeed portlets...then they
> again require authentication....
> can anyone please tell me how to do away with this double effort...i mean
> one authentication for both jetspeed and the associated portlets'
> applications...
>
This is near impossible in complicated environments, especially if you don't
have already a single authentication system in place.
The current proposed methodology is to store in the user object (or the PSML
parameters as you prefer) a "password keyring".
Whenever a user will first include a portlet in the portal page, it'll have to
authenticate against his legacy application, but these authentication tokens
will be saved by the portlet in PSML or User data and retrieved when needed.
This is not as good as a complete user database integration, but it works and
is manageable.
--
Raphael Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Paris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
