> > What are some of the known implications with starting CF 
> > as another user, if any? I need access to a file on 
> > another server for one very small component, and am 
> > trying to weigh the pros/cons of using either a network 
> > share, or going through FTP. If I understand correctly, 
> > in order to use a network share you have to start CF 
> > with an account that has the proper permissions on that 
> > share.
> > 
> > This will be a file that needs to be updated fairly 
> > frequently: 10 - 50 times per day. What would you do?
> 
> Yes, to use a Windows Networking share, you'll need CF to run 
> as a user which can see the share. To run CF as a different 
> user, you'll need to make sure that the user account has 
> permissions on all the right files and registry keys. There's 
> a good writeup of this for CF 5 here:
> 
> http://www.defusion.com/articles/index.cfm?ArticleID=89
> 
> It's actually quite a bit easier with CFMX, since there's no 
> significant registry data - just ensure that the CFMX user 
> account has rights to the \CFusionMX directory and your .cfm 
> files, more or less.
> 
> However, granting this user account rights to your network 
> might be a security issue. That's really up to you to decide.

One thing I forgot to mention; you might want to run CF as a specific user
account anyway, just to limit other security problems.

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Your ad could be here. Monies from ads go to support these lists and provide more 
resources for the community. http://www.fusionauthority.com/ads.cfm

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to