Using the defaultProvider Parameter

  • Article

In Scenarios 2 and 3, the defaultProvider parameter identifies the provider for the AgentLoginManager Web service. The defaultProvider value is located in the Web.config file for the AgentLoginManager, which is located in <InstallDir>\Inetpub\wwwroot\Microsoft.Ccf.Csr.WebServices.ContactCenter.AgentLoginManager

The default provider section uses the following pattern.

<providers>
<add name="name" type="type" connectionString="Connection String"/>
</providers>

There are two default providers for this Web service:

  • WindowsAuthenticationProvider – This provider compares the logon data with the authentication data that is stored in the CCF Active Directory. This provider is used in Scenario 2 described at the beginning of this section.
  • CustomAuthenticationProvider – This provider compares the logon data with authentication data stored on a third-party directory service or a non-trusted Active Directory. After the directory service verifies the authentication data, it passes the data to the CCF Active Directory. This provider is used in Scenario 3.

The following code is an example of the provider configuration XML code.

<!--Agent Login Manager-->
<Csr.WebServices.Providers.ContactCenter.AgentLoginManager.AgentLoginManager defaultProvider="WindowsAuthenticationProvider">
<providers>
<add name="WindowsAuthenticationProvider" type="Microsoft.Ccf.Csr.WebServices.Providers.ContactCenter.WindowsAuthenticationProvider,Microsoft.Ccf.Csr.WebServices.Providers" connectionString="Server=CCFSQL;Integrated Security=true;Database=CCFInfrastructure;Pooling=false"/>
<add name="CustomAuthenticationProvider" type="Microsoft.Ccf.Csr.WebServices.Providers.ContactCenter.CustomAuthenticationProvider,Microsoft.Ccf.Csr.WebServices.Providers" connectionString="Server=CCFSQL;Integrated Security=true;Database=CCFInfrastructure;Pooling=false"/>
</providers>
</Csr.WebServices.Providers.ContactCenter.AgentLoginManager.AgentLoginManager>

The Agent Desktop reads any changes to the AgentDesktop.exe.config file, and it operates according to the changes. However, if the project is rebuilt, the binaries are created in the Agent Desktop bin\debug or the bin\release folder. In the process, the original, unchanged App.config file from the project code is copied to the output folder as AgentDesktop.exe.config. Agent Desktop will use this configuration file if it runs from the output directory.