This article explains the types of security that are available for the Task Server’s Notification Server (NS) and Site Servers and how they are supported.
The Task Server connects to the NS using the same URL that the agent on the machine is using. For example, if the agent uses HTTPS so will task server.
The Task Server verifies the NS’s server certificate using .NET mechanisms. These mechanisms are the same as the ones that the agent uses.
These mechanisms are:
Since the Task Server does not care what type of bindings are configured in IIS, HTTPS-level access to clients is available. The Task Server can be accessed through HTTPS or HTTP if IIS allows the Task Server’s website to be accessed that way. The agent talks to the NS according to the configured NS URL.
When the communicating to the Task Server, the following rules apply:
When handling custom port numbers, the following rules apply:
Note: Tickle connections between the Task Server and NS as well as between the Agent and Task Server are not secured by SSL.