This behavior is determined by enabling the AgentNamesAreFQHostNames configuration parameter. This parameter is disabled by default, so the credential collector uses the value of the DefaultAgentName parameter as the agent name.Ĭonsider the previous implications before configuring credential collectors in a mixed environment. To process requests, the FCC and NTC rely on the user credentials and the name of the Web Agent that is protecting the requested resource.
The following configuration options help FCCs and NTCs to operate with 4.x Web Agents: However, 4.x agents and third-party agents posting to the FCC and NTC do not pass the Agent name on the URL they send.
Use Compatibility Mode-to enable a r5.x, r6.x, or 12.52 SP1 FCC/NTC to serve up forms for resources that are protected by 4.x agents or third-party applications, then enable the FCCCompatMode parameter. Traditional Web Agents have the FCCCompatMode parameter is enabled by default. Framework Agents have the FCCCompatMode parameter is disabled by default.Įnabling this parameter makes a r5.x, r6.x, or 12.52 SP1 Agent handle forms and NTLM credential collection like a 4.x Agent. This setting which means that a form or NTLM credential cookie is written to the browser of the user is redirected back to the Agent before logging in.
This configuration permits the agents to interoperate. When the value of the FCCCompatMode parameter is set to no, compatibility with 4.x Agents is disabled. In an 12.52 SP1 environment, set the value of the parameter to no.
0 kommentar(er)
