We are changing all of our servers to use the credentials in the Logon As of the service, rather than as a VisualCron Credentials property. This will make management and migration of the Jobs much easier. This has worked great, until we got to the server that matters most.

We run about 50 of these HTTP tasks (50 jobs, 1 task per job.) These are all failing. Does the HTTP task not use the Service credentials (like all other tasks seem to)?

I can confirm what I suspected to be the case. All other tasks that require Credentials (for example to access to network shares) work fine. The only jobs that fail are the ones that use HTTP tasks.

As authentication is not just done by Windows authentication (in HTTP you have Basic and Forms as well) running the service as another user will only help when using Windows auth.

---

But that is what we are using, Windows Authentication (only.)

When I look at it closer there is more to it. It is not just the context that needs to be right but behavior also changes when you select a Credential.

---

When I look at it closer there is more to it. It is not just the context that needs to be right but behavior also changes when you select a Credential.

I'm not sure what that means, but we still have a huge problem in that we are about to migrated about 50 tasks to a new machine and the credentials don't carry over.

On a good note, I successfully updated a bunch of tasks using C# and the API - that might solve many of our problems.

Ok, it means that when using Windows Credentials over the Internet, as in the HTTP case, it is very different as most or many Internet services do not use Windows authentication at all, but authentication on another level.

---

Ok, it means that when using Windows Credentials over the Internet, as in the HTTP case, it is very different as most or many Internet services do not use Windows authentication at all, but authentication on another level.

This process works fine when I set the credential in the task. I just don't understand the different between the two and why most tasks work fine with using the Service's credential instead.

When running a service, or any process, as a Windows user you run simply as that Windows user using Windows authentication. When you are executing something, like the HTTP Task it may not use Windows authentication at all (depending on remote site). This results in using "wrong" authentication method which does not help the HTTP authentication at all.

---

When running a service, or any process, as a Windows user you run simply as that Windows user using Windows authentication. When you are executing something, like the HTTP Task it may not use Windows authentication at all (depending on remote site). This results in using "wrong" authentication method which does not help the HTTP authentication at all.

But that still does not explain why. I know for a fact that all other task function fine, including using the Service account's profile and have full access to all network resources. I feel like this is a bug.

I don't think I explain this in any other way without being too technical. Perhaps somebody else can jump in and explain this more.

This is not a bug.

---