Re: Credentials for remote web service

David,
I think, the easiest way is to keep the credentials in the
PortletSession. The question here is how to persist it ? 

Another option is user attributes. But then I have to declare it for
each portlet application. Is that right ? 


On Mon Aug 29,2011 10:24 pm, David Taylor wrote:
> On Mon, Aug 29, 2011 at 9:09 PM, Mansour Al Akeel
> <[email protected]> wrote:
> > David,
> > I missed the part about init-param. I am not sure, how to set them. My
> > understanding they are set in the portlet.xml file ! Could they be
> > specific for each user ?
> 
>  init-params are not specific for each user.
> 
> >
> >
> >
> >
> > 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]
> >
> >
> 
> 
> 
> -- 
> David
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>