portal entry

select a category, or use search below
(searches all categories and all time range)
Title:

Apply the Server Auto-Lockdown to a site without re-installing the Lockdown tool

| View in Portal
September 25, 2019 12:19:40 PM GMT
2 Comments 
<p>The Server Auto Lock-Down installer does not allow you to apply lock-down for newly created sites without re-installing the lock-down tool from the beginning. Follow the procedure to re-install the lock-down tool for a new site. Assumptions ColdFusion is configured with one site cfsite1, and the runtime user name of ColdFusion after lockdown is cfuser. In addition, you have already locked down the instance cfusion (located as C:\ColdFusion2018\cfusion). The magic folder path for the site is C:\ColdFusion2018\config\wsconfig\1 You have a second site called cfsite2, which […]</p>
<p>The post <a rel="nofollow" href="https://coldfusion.adobe.com/2019/09/apply-server-auto-lockdown-site-without-re-installing-lockdown-tool/">Apply the Server Auto-Lockdown to a site without re-installing the Lockdown tool</a> appeared first on <a rel="nofollow" href="https://coldfusion.adobe.com">ColdFusion</a>.</p>
Labels: Adobe ColdFusion 2018, Blog, Auto-Lockdown installer, Server Auto-Lockdown

Comments:

There seems a slight mistake that could confuse readers. In your reference to the new connector "magic folder" for the new "site 2", you refer to its as folder 3 in the first reference, but folder 2 in the second: <em>Create a connector for the website cfsite2, which has a magic folder, for example, C:\ColdFusion2018\config\wsconfig\3.</em> But later: <em>Navigate to the magic folder for cfsite2 (C:\ColdFusion2018\config\wsconfig\2) and open the file worker.properties.</em> Also, the first one reads as if they user SHOULD set it to 3, but of course we have no control of that. Really, it should tell the reader look to see what number the folder is for their new site and new connector. That can be seen in the Jakarta virtual directory or alias created in the web server for that site. You may also want to point readers to Adobe resources with more details on how the wsconfig files all connect. I'll add that those who may need assistance with this sort of stuff can get directed remote help (for a fee) from Adobe support or folks like myself. I list such troubleshooting consultants at cf411.com/cftrouble. Sometimes it would take only minutes for an experienced person to sort out a confusing, misconfigured setup. It is indeed unfortunate that this stuff can be so complex.
Comment by Charlie Arehart
2324 | September 25, 2019 01:03:15 PM GMT
Thanks a lot Charlie.
Comment by SauravGhosh
2329 | September 26, 2019 05:03:12 AM GMT