Results 1 to 5 of 5

Thread: Settings you should enable within your local ColdFusion Administrator

  1. #1
    Join Date
    Nov 2009
    Posts
    99

    Default Settings you should enable within your local ColdFusion Administrator

    When developing on a local ColdFusion server, most developers accept the default Coldfusion Administrator settings that are set by the ColdFusion installer. This is fine for development servers, but it can cause some problems when moving a ColdFusion application into production in a shared hosting enviroment. To ensure your code runs well when you move it to our servers, we recommend you make the following adjustments within your local ColdFusion Administrator:

    First, on the Settings page make sure you enable the setting that says: "Disable access to internal ColdFusion Java components" (pictured below)




    Second, under the Security Tab click the Sandbox Security link then click the box to "Enable ColdFusion Security". (pictured below)




    Once Sandbox Security is enabled, you'll need to create a sandbox for your local site. To do this, add the full path to your site below where it says "Add Security Sandbox", then click "Add". For example if you are using the default site location for IIS, you would use 'C:\inetpub\wwwroot' as shown below:




    The last thing to do is add the correct paths and permissions. By default, ColdFusion will add the path to your site, but you'll also want to make sure the following paths/permissions are added too (permissions are listed in parentheses next to path):

    • C:\ColdFusion9\cache\- (Read,Write,Delete)
    • C:\WINDOWS\Fonts\- (Read)
    • C:\ColdFusion9\wwwroot\WEB-INF\cfclasses\- (Read,Write)
    • C:\ColdFusion9\wwwroot\WEB-INF\cftags\interface.cfc (Read)
    • C:\ColdFusion9\tmpCache (Read)
    • C:\ColdFusion9\tmpCache\- (Read,Write,Delete)
    • C:\ColdFusion9\runtime\servers\coldfusion\SERVER-INF\temp\wwwroot-tmp\- (Read,Write,Delete)
    • C:\ColdFusion9\runtime\servers\coldfusion\SERVER-INF\temp\wwwroot-tmp (Read)
    • C:\ColdFusion9\tmpCache\CFFileServlet\_cf_image\- (Read,Write,Delete)
    • C:\Users\USERNAME\AppData\Local\Temp\- (Read,Write,Delete)*


    Please note, this assumes you're using a recent version of Windows (Vista or newer), and that ColdFusion is installed to 'C:\ColdFusion9'. If on an earlier version of Windows, the only thing you'll do differently is replace 'C:\Users\USERNAME\AppData\Local\Temp\-'* above with this path: 'C:\DOCUME~1\USERNAME\LOCALS~1\Temp\-'*

    *Replace USERNAME with the actual name of your ColdFusion runtime user.
    Last edited by jakeh; June 5th, 2011 at 11:01 PM.

  2. #2
    Join Date
    Jul 2011
    Posts
    4

    Default Where do we add the paths?

    In the Administrator, how do we add the paths?

  3. #3
    Join Date
    Aug 2009
    Posts
    60

    Default

    Hello,

    To add paths to your sandbox security once logged into your ColdFusion admin you will click on the "Security" tab, then choose "Sandbox Security". Locate your domain under "Defined Directory Permissions", click on your domains link, then choose the "Files/Dirs" tab. Here you can add your file paths and set the correct permissions for them. Once the path is in the text box "File Path" and you have choose your permissions click the "Add Files/Paths" button.

  4. #4
    Join Date
    Dec 2012
    Posts
    1

    Default Is the flash services gateway affected by these setting?

    Quote Originally Posted by jakeh View Post
    When developing on a local ColdFusion server, most developers accept the default Coldfusion Administrator settings that are set by the ColdFusion installer. This is fine for development servers, but it can cause some problems when moving a ColdFusion application into production in a shared hosting enviroment. To ensure your code runs well when you move it to our servers, we recommend you make the following adjustments within your local ColdFusion Administrator:

    First, on the Settings page make sure you enable the setting that says: "Disable access to internal ColdFusion Java components" (pictured below)




    Second, under the Security Tab click the Sandbox Security link then click the box to "Enable ColdFusion Security". (pictured below)




    Once Sandbox Security is enabled, you'll need to create a sandbox for your local site. To do this, add the full path to your site below where it says "Add Security Sandbox", then click "Add". For example if you are using the default site location for IIS, you would use 'C:\inetpub\wwwroot' as shown below:




    The last thing to do is add the correct paths and permissions. By default, ColdFusion will add the path to your site, but you'll also want to make sure the following paths/permissions are added too (permissions are listed in parentheses next to path):

    • C:\ColdFusion9\cache\- (Read,Write,Delete)
    • C:\WINDOWS\Fonts\- (Read)
    • C:\ColdFusion9\wwwroot\WEB-INF\cfclasses\- (Read,Write)
    • C:\ColdFusion9\wwwroot\WEB-INF\cftags\interface.cfc (Read)
    • C:\ColdFusion9\tmpCache (Read)
    • C:\ColdFusion9\tmpCache\- (Read,Write,Delete)
    • C:\ColdFusion9\runtime\servers\coldfusion\SERVER-INF\temp\wwwroot-tmp\- (Read,Write,Delete)
    • C:\ColdFusion9\runtime\servers\coldfusion\SERVER-INF\temp\wwwroot-tmp (Read)
    • C:\ColdFusion9\tmpCache\CFFileServlet\_cf_image\- (Read,Write,Delete)
    • C:\Users\USERNAME\AppData\Local\Temp\- (Read,Write,Delete)*


    Please note, this assumes you're using a recent version of Windows (Vista or newer), and that ColdFusion is installed to 'C:\ColdFusion9'. If on an earlier version of Windows, the only thing you'll do differently is replace 'C:\Users\USERNAME\AppData\Local\Temp\-'* above with this path: 'C:\DOCUME~1\USERNAME\LOCALS~1\Temp\-'*

    *Replace USERNAME with the actual name of your ColdFusion runtime user.
    I have developed a browser based application that is trying to access a .CFC on another server. The gateway connection fails going across our network. Are there settings inside the administrator that may affect access to CFCs or <cfcomponent> tags?

  5. #5
    Join Date
    Nov 2009
    Posts
    99

    Default

    It sounds like there might be a lower-level permissions going on, so make sure your network drives are mapped properly with appropriate permissions.

    The only place in CF that would affect this is Sandbox Security (so you may want to check Sandbox settings too).

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •