ColdFusion 9.0.1 post chf9010002 update

Report · Nov 02, 2011

There seems to be yet another bug in the latest RE-released hot fix 2 for ColdFusion 9.0.1. We discovered that the Scheduled Task is no longer passing the Username correctly to IIS 6.0 using Basic Authentication. When you add the Username to the field "DOMAIN\Username" with the password and hit submit, then reenter to look at the details of the scheduled task, you find the format has changed to "DOMAINUsername" and continues to generate a 401 in IIS (/applicationfolder/applicationfile.cfm - 82 DOMAINcfadmin_account XXX.XX.XXX.XX CFSCHEDULE 401 1 1326). The settings in IIS are set to allow Basic Authentication and doesn't appear to be the source of the problem, rather the CFAdmin is not handling the Domain\Username credentials that are entered in correctly? In this particular case, my developers state that they need the Scheduled Task to run under that account as they are using the credentials in the methods that are being invoked. None the less, something has changed yet again that creates an impact to the environment as a result of this Hot Fix, which I have had to apply several times in 2 iterations now? Any ideas? or does it need to get officially submitted to Adobe for resolution?

Report · Nov 02, 2011

Hi,

Try set User Name to user@domain rather than domain\user.

That worked for me when I tested on :

Server Settings > Settings Summary > System Information

Server Product ColdFusion

Version 9,0,1,274733

Update Level /C:/ColdFusion9/lib/updates/hf901-00002.jar

HTH, Carl.

Report · Nov 03, 2011

Thanks Carl for the suggestion, thought I had already tried that, so I tried it again and still a 401. Have you installed the CHF9010002 rereleased Hot Fix and tried it again? I also didn't recall coming across this in the previously released Hot Fix (hf901-00002.jar), so I'm assuming that you are saying that it was a problem even in the earlier release? For the most part I have been transitioning my environments Scheduled Task to not require Authentication and isolating the "Scheduled Pages" into there own directory so I can control access if need be. But this being a dedicated environment where this problem exist, it's up to the developer to determine how that is going to function based on how they have coded there app and what methods they are using to accomplish there task. Sounds like it's time to get wrapped around opening a ticket with Adobe now. thx

Report · Nov 04, 2011

I found a work around to this issue by using the files that are in the CFIDE\administrator\scheduler directory prior to any Hot Fixes. I presume the issue lies in 1 of 2 files:

HotFix 2 Files Prior to Hot Fix 2

Scheduleedit.cfm 90kb Scheduleedit.cfm 87kb diff

Scheduletasks.cfm 82kb Scheduletasks.cfm 74kb diff

Report · Nov 06, 2011

Perhaps should be reported as bug, here - http://cfbugs.adobe.com