Scheduled Task Calling Password Protected Page

Ok, I understand that a page that is called via a Scheduled Task cannot redirect, such as redirecting to a login page. I created a folder called tasks and placed the page to be called inside of it. I set anonymous permissions to deny and allowed a certain user read and write access. In the Control Panel I placed the username and password for the scheduled task, but it does not run. If I set the permissions to anonymous access it works.

What am I doing wrong?

 

Ok, I am sorry, that was my original problem.


Ok, here is the current problem. The scheduled task runs fine and the page is password protected using the permissions manager. The problem is that an anonymous user can still get to the page just by typing the url in the address bar of IE. I created a support ticket for this and the response was that I had to use windows authentication in my asp.net application. This is not feasible since I am already using forms authentication with a membership api for the site. Any other ideas.

 

I'm a little confused. If you have membership/roles setup on your directory then no one should be able to gain access to the page with out the proper creditials. If hte page that the schedule task is tirggering resides in it's own subdirectory, you should be able to configure it as a web applicaiton folder using the Web Application Tool inside the dasp control panel. You can then create a web.config file for that subdirectory sepicifying windows authentication mode. This should not affect your other web applications that reside out of this subdirectory.

 

Ok, that sounds like a reasonable option. The page that the task runs is in its own directory and does not require forms authentication to access it because the Scheduled Task Manager cannot call a page that will redirect to the login page (forms authentication). I will try the Web Application for the folder so I can use windows authentication.


Thanks!!

 

Thank you very much!!!


Works perfectly now that I made the Tasks folder it's own web application with its own web.config file specifying windows authentication.