You can do a straight forward username/password system for your webservice. In that if they do not have the correct username and password, they just don't get it.
You can use the CFLOGIN system to secure webservices from memory. It has the same concept for FlashRemoting in mind, in that you can send username/passwords via flash remoting to your gateway so it making use of the same CFC should in theory have a lockdown capability in place. XML being a human readable language means in a nutshell, encrypting it etc would defeat the purpose. I haven't personally seen anyone secure it other then maybe locking down the directory with IIS or changing the mypacket.xml to mypacket.cfm and doing its own "Security" logic within. If you find a way, share it :D as i'd be interested in seeing how they do it. Scott "Jeremy" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > Howdy all, > > This morning seems to be longer then most this week. I'm hanging for the day > to end so I can go back to bed. Nevertheless, my curious to get my hands on > some information about securing XML. Being really new to the whole XML thing > I wondered if anyone out there could point me in the right direction to > securing a connection from a CFC Webservice to a database. > > In the end I want to pull data out of one database using CFC Webservice then > transfer it into another DB. > > Any suggestions would be good. > > Jeremy > > > > --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MX Downunder AsiaPac DevCon - http://mxdu.com/
