Configuring SQL Authentication

By default, Enterprise Server for .NET connects to SQL Server using Windows authentication (SSPI), with user login credentials.

You can configure the installation to connect to the database using supplied SQL Server authentication and credentials instead of user login credentials.

This method is useful in situations where:

Your installation connects to a database on a different system, and you are running in a workgroup rather than a domain.
For security, you need to have Enterprise Server for .NET use a different account when connecting to the database.

Set the database authentication details to use in machine.config.

Important: Use this process when an installation accesses database servers located on remote machines that use different login credentials. If an event monitor attempts to access a database server on a remote machine for which it has no access, the attempt fails.

Note: If your installation uses Windows authentication for SQL Server, ensure that the event monitor service (seemonitor.exe) and the IIS application pool used by Enterprise Server for .NET are configured to run as a Windows user that has database administration privileges for each of the region databases that are to be accessed.

Example machine.config file

The following is an example machine.config file configured for SQL authentication:

<configuration>
  ...
  <configSections>
    ...
    <!-- Added for Micro Focus SEE for .NET -->
    <section name="MicroFocus.SEE" 
             type="MicroFocus.SEE.Utils.GlobalConfigurationSection,
             MicroFocus.SEE.Utils,Version=4.0.0.0,
             Culture=neutral,PublicKeyToken=0412c5e0b2aaa8f0" />
    ...
  </configSections>
    ...
  <!-- Added for Micro Focus SEE for .NET -->
  <MicroFocus.SEE>
    ...
    <add key="SQL.credentials" value="User ID=abc;password=xyz"/>
    ...
  </MicroFocus.SEE>

</configuration>