> idea. My SecureServiceLocator class can request the
> credentials inside of getService() instead of implementing it's own
> setUsernamePassword() method.
>
> What do you think?
I like it...
> > So are you keeping passwords unencrypted on the client ?
>
> For now, I am. I don't want the user to have to input their
> credintials for every request made to a secure remote object.
> Do you have any suggestions?
The more I think about it, I don't think it's an issue ... they're
not statically compiled in, so it's only once the user has offered
those credentials, they are essentially cached in memory for the
lifetime of their session. The security concern is really the
data going over the wire, and that's not a Flex problem, and it's
one easily solved (HTTPS, etc).
Good job !
Steven
--
Steven Webster
Technical Director
iteration::two
This e-mail and any associated attachments transmitted with it may contain
confidential information and must not be copied, or disclosed, or used by
anyone other than the intended recipient(s). If you are not the intended
recipient(s) please destroy this e-mail, and any copies of it, immediately.
Please also note that while software systems have been used to try to ensure
that this e-mail has been swept for viruses, iteration::two do not accept
responsibility for any damage or loss caused in respect of any viruses
transmitted by the e-mail. Please ensure your own checks are carried out
before any attachments are opened.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
