Use SCCs in a Mixed Environment

To enable 4.x Web Agents and r5.x, r6.x, or r12.0 SP2 SCCs to interoperate, do one of the following:

Specify Agent name mappings: Map the AgentName parameter to the host name and IP address of each host using that SCC for its protected resources. You set up these mappings in the SCC's Agent configuration file or its Agent Configuration Object at the Policy Server.
Use Host Names as Agent Names: If you do not specify Agent name mappings, you can set the AgentNamesAreFQHostNames parameter to Yes. This tells the SCC to use the fully qualified host name in the target URL as the Agent name.
For example, if the URL string is:

url?A=1&Target=http://www.nete.com/index.html

The www.nete.com portion of the Target string serves as the Agent name.

By default, this parameter is set to no. Consequently, the value of the DefaultAgentName parameter is used as the Agent name.

The following table shows how 4.x and r5.x, r6.x, or r12.0 SP2 Agents acting as SCCs operate in a mixed environment:

Web Agent Version	4.x QMR 2/3/4 SCC	r5.x, r6.x, or r12.0 SP2 SCC
4.x QMR 5 or 4.x QMR 6	Agent issues an SSL credential cookie. Certificates cannot be collected without redirecting requests, even if the original connection from the browser to web server is over SSL.	Create mappings in AgentName parameter or set AgentNamesAreFQHostNames to Yes. SCC issues a session cookie Certificates cannot be collected without redirecting requests, even if the original connection from the browser to web server is over SSL.
r5.x, r6.x, or r12.0 SP2	Agent issues an SSL credential cookie. Certificates can be collected without redirecting requests.	SCC issues a session cookie Certificates can be collected without redirecting requests.

Note: For more information about SSL Authentication Schemes, see the Policy Server documentation.