Hello David, I didn't look deeply into this option. My understanding it supports basic, form, and cookies authentications.
Here are the pages I looked into http://portals.apache.org/jetspeed-2/deployguide/config-sso.html I found the closest thing to what I want is CAS filter. But again, the authentication in the system I need to connect is done by passing credentials with each call, so this may not work, and still I don't know where to store the credentials. I am looking now at the javadoc for SSO. I am not sure if there's introductory examples. In all cases, I will continue looking at these doc. Thank you. On Mon Aug 29,2011 08:24 pm, David Taylor wrote: > Well there are init-parameters, but they are not secured. Have you > looked at using the Jetspeed SSO API? > > http://portals.apache.org/jetspeed-2/apidocs/org/apache/jetspeed/sso/package-summary.html > > Also look at the SSO Administrative Portlet for examples of using the API > > http://portals.apache.org/jetspeed-2/adminguide/sso.html > > On Mon, Aug 29, 2011 at 7:32 PM, Mansour Al Akeel > <[email protected]> wrote: > > We have many web services that takes the user name and password as > > parameters. I need to write portlets to display the results for each web > > service. I am not sure about the best way to store these credentials. > > > > I can not use portlet prefrence, because there are many portlets. So it > > looks silly to enter the username/password as a prefrence for each of > > them, and modify them, when the remote system creadentials change. > > > > > > Any idea? > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > > -- > David > > --------------------------------------------------------------------- > 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]
