Manage Database Connections

Use this feature to create and manage database connections for FlowWright.

Last published at: September 22nd, 2026

DB connections can be managed through the following user interface:

Navigate to the Integration > Connections page. 

 

The Manage Database Connections page is shown below. 

 

Select Connections to navigate to the “OAuth, RabbitMQ, FTP, SFTP, and Generic” connections page.   

 

Select Connections to navigate to the “Create, Edit, Remove, Test, and Copy” connections page.   

 

Select Utils to navigate to the “DB Details, and Update Report Connections” features. 

 

Create DB Connection. 

Click Actions > Create. 

 

A pop-up window opens for configuration. Enter the DB Connection name. Select the connection type (SQLClient, OLEDB, or MongoDB) from the drop-down list. Switch OFF the connection string builder. Enter the connection string as shown in the example below. Click the Test button. If the connection string is valid, a confirmation message appears in the top-right corner.     

 

Click the Create button. The DB Connection name is created successfully. 

 

Select the Connection String Builder as “ON” to view the following UI. Enter the SQL Server Name, Database Name, User Name, and Password as shown below. Select the authentication type as “SQL Server” or “Windows”.  Click the Test button to validate the configuration. A confirmation message appears in the top-right corner. Click the Generate button. A new database connection is created and added to the table list. 

 

For Windows Authentication, provide the Server Name and Database Name. Click the Test button to validate the configuration. A confirmation message appears in the top-right corner. 

 

Note: Configuring Windows Authentication (Integrated Security) between IIS and SQL Server allows your web application to connect securely without hardcoding database credentials in a configuration file. The industry-standard, most secure approach is to use a Domain Service Account via the IIS Application Pool Identity. This avoids the security risks and configuration complexities associated with Kerberos double-hop impersonation.

Step 1: Configure the IIS Application Pool Identity

By default, application pools run under restricted local accounts (like ApplicationPoolIdentity) which cannot authenticate across a network to a remote SQL Server.

  • Open Internet Information Services (IIS) Manager.
  • Click Application Pools in the left connections pane.
  • Right-click your application's pool and select Advanced Settings...
  • Under the Process Model section, click on Identity and select the ... button.
  • Select Custom account, click Set, and enter the credentials for your Active Directory domain account (e.g., DOMAIN\DatabaseUser).
  • Click OK to save and apply

 

Step 2: Grant Permissions in SQL Server

The Windows account running your IIS application pool must be given explicit rights inside SQL Server.

  • Open SQL Server Management Studio (SSMS) and log in. 
  • Expand the server node, right-click the Logins folder, and select New Login... 
  • Keep Windows authentication selected and enter your domain account (DOMAIN\DatabaseUser) into the Login name box. 
  • Go to the User Mapping tab in the left-hand pane. 
  • Check the box next to your target database, and in the lower pane, assign the appropriate database roles (such as db_datareader and db_datawriter). 
  • Click OK to create the login. 

 

Step 3: Update the Web Application Connection String

Configure your application's connection string to tell the database provider to use Windows Identity instead of a standard username and password. 

Modify your web.config or appsettings.json file to include Trusted_Connection=True; or Integrated Security=True;.

<connectionStrings>
  <add name="MyDatabase" 
       connectionString="Server=SQL_SERVER_NAME;Database=MyDatabaseName;Integrated Security=True;TrustServerCertificate=True;" 
       providerName="System.Data.SqlClient" />
</connectionStrings>

 

Alternative Scenario: IIS and SQL Server on the Same Machine

If your IIS server and SQL Server are running on the exact same physical or virtual machine, you can skip creating a domain account.

  • You can leave your Application Pool Identity set to the default built-in account (ApplicationPoolIdentity or NetworkService). 
  • Inside SQL Server, simply map permissions to the local system group: IIS_IUSRS or the virtual account IIS APPPOOL\YourAppPoolName.

 

Edit DB Connection. 

Select the connection from the table, then click Actions > Edit. 

 

A pop-up window opens for modification. Make the necessary changes, then click the Test button to validate the connection. A confirmation message appears in the top-right corner.  

 

Click the Update button to confirm the changes. Another confirmation message appears in the top-right corner.

 

Test DB Connection. 

Select the connection from the table, then click Actions > Test.

 

The connection string is validated, and a confirmation message appears in the top-right corner. 

 

Copy DB Connection. 

Select the connection from the table, then click Actions > Copy.

 

Provide a new connection name. Click the “Copy” button. 

 

A copy of the DB connection is created in the background, and a confirmation message is shown in the top-right corner. 

 

Remove a DB Connection. 

Select the connection from the table, then click Actions > Remove.

 

A pop-up window appears for confirmation. Click OK to continue. 

 

The database connection is permanently removed, and a confirmation message appears in the top-right corner. 

 

Database details.

Use this feature to view the database tables and their structures. The table lists the connection names, as shown in the UI below.

Select the DB connection from the table on the Manage Database Connections page, then click the Utils > DB Details menu option.   

 

The table names for the selected database connection are displayed in the new pane. Select a table to view its column names and data type information. Use the Search textbox to filter the table list.  

 

Update Report Connection configuration.

The config file (in the application root folder) contains all connection strings used by the UI and the engines.

On the Manage Database Connections page, select Utils > Update Report Connections to update all stored connections in this file. 

 

A confirmation message appears in the top-right corner.