You can add remote credentials for a Jetspeed group or user to the credential store.
Look at the SSO portlets how to use the credentials store.
We use SSO to manage db credentials and web access. We attach remote credentials to groups (e.g Application1, Application2,..) and then assign users to that group. If a user logs into Jetspeed and tries to access a protected application/site it will use the remote credentials if the user is a member of the group.
Roger
Jeff Linwood wrote:
Hi,
One approach would be for your portlet to use the portlet API's user preferences to store the user's username and passwords for each of the portlet applications. The user would authenticate to Jetspeed (or any other portlet-API compatible portal), and then the portlets would log the user in from the stored username and password in preferences.
Jeff
On 4/15/05, Jonathan Hawkins <[EMAIL PROTECTED]> wrote:
We are using Jetspeed as a window into our different applications. Each applkication requires a silent login which we have partially solved with some drawbacks.
I am looking at providing a single sign on solution that can be shared by each application, the user signs into Jetspeed and then each application can authenticate against the single sign on solution.
Has anybody any experience of this or suggestions. I have found a particularly interesting article here, http://www-106.ibm.com/developerworks/web/library/wa-singlesign/
One requirement would be the ability to deploy the SSO solution ina any portal !!
Would be interested in your views
Jon Hawkins
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]