- 6 minutes to read

Prerequisites for the Nodinite Web Client

This page details the essential prerequisites for installing and running the Nodinite Web Client. Ensure your environment is ready for a secure, high-performance deployment.

✅ Modern browser support for the best user experience
✅ Clear checklist for Windows rights and firewall settings
✅ No SQL Server rights required for the Web Client
✅ Security best practices and troubleshooting tips

The Nodinite Web Client (versions 1-6) is a Web Application hosted in IIS on a Windows Server. The binaries ship with the Nodinite Core Services package.

graph LR subgraph "Consumers" roBrowser[fab:fa-chrome Chrome
fab:fa-firefox Firefox
fab:fa-edge Edge
fab:fa-safari Safari] end subgraph "Web Server" roWebClient(fal:fa-globe Web Client) ---roWebAPI(fal:fa-cloud-sun Web API) roBrowser ---roWebClient end

Diagram: Supported browsers and Web Client communication with Web API.

Internet Explorer provides a limited experience and is partially supported using Nodinite 5.3 and older. Version 5.4 and later does not support Internet Explorer at all.

Verified Topic
IIS Windows Features
Supported Client Browser
Windows rights
Firewall

Use the checklist above to ensure a successful deployment of Nodinite.

IIS Windows Features

The Nodinite Web Client is an IIS-hosted web application built on .NET 9 and ASP.NET Core (Nodinite 7) or .NET Framework 4.8 (Nodinite 6).

Key requirements:

  • Windows Authentication - Required for integrated security
  • ASP.NET Core Module V2 - Required for Nodinite 7 (.NET 9)
  • ASP.NET 4.x / .NET Extensibility 4.x - Required for Nodinite 6 (.NET Framework 4.8)

IIS Windows Features - Complete feature list, installation scripts, and troubleshooting

Important

The Default Web Site must exist within IIS. The Nodinite installer will fail if this is missing.

Supported Client Browser

The Nodinite Web Client requires a modern HTML-5 enabled browser. Different browsers may render content differently, so your experience may vary depending on your choice.

Browser Minimum Supported Version Recommended version Note
Chrome 48 Latest Recommended
edge 12 Latest Recommended
Safari 5 Latest
Firefox 37 Latest
Internet Explorer* About Lifecycle LIMITATIONS EXISTS - We do not recommend the usage of IE. Some features like Swagger are not supported. Nodinite 5.4+ does not render well in Internet Explorer and is not supported for use with Nodinite

/* Internet Explorer 9 and 10 were supported with Nodinite version 1-4. Nodinite 5, requires a modern HTML-5 browser.

We develop and test Nodinite using Chrome and Edge to give you the best and richest experience. Our recommendation is to stick with these options.

What Windows rights does the Web Client require?

The Nodinite Web Client runs as an IIS web application with a dedicated App Pool. The v7 PowerShell installation scripts automatically configure these settings during installation.

Service Account Requirements:

  • The App Pool service account must be able to login to the server: Allow Logon locally
  • If the service account is not a local administrator, it must be a member of the IIS_IUSRS group
  • The service account must have Read rights on %windows%\system32\inetsrv\config folder (for redirection.config access)

Note

To grant a user account the ability to log on locally to a domain controller, you must make that user a member of a group that already has the "Allow logon locally" system right, or grant the right to that user account directly.

How It Works:

The v7 PowerShell installation scripts create a dedicated IIS App Pool for the Web Client. This App Pool runs with ASP.NET Impersonation enabled, which means:

  • The App Pool runs with the configured service account identity
  • When end-users access the Web Client, their Windows credentials are used to authenticate with IIS
  • Calls to the Web API retain the end-user's identity for role-based access control

IIS Authentication settings - Complete guide to authentication configuration, troubleshooting, and encryption

Tip

Troubleshooting permissions: If you encounter "Cannot read configuration file due to insufficient permissions" errors, ensure the App Pool account has Read rights on %windows%\system32\inetsrv\config. See the IISConfigurationFile troubleshooting guide.

What are the required Firewall settings for the Web Client?

The Nodinite Web Client requires open ports for both inbound and outbound communication.

Three servers commonly participate in Web Client deployments; plan firewall rules for each:

Server Role
Web Server Hosts the Web Client and Web API (IIS)
SQL Server Hosts Configuration and Log Databases (queried via Web API)
Domain Controller Provides Kerberos authentication and DNS services

Plan firewall rules for communication between these servers (Web Server ↔ SQL Server, Web Server ↔ Domain Controller, SQL Server ↔ Domain Controller). End-users access the Web Client from their browsers over HTTP/HTTPS.

Note

Nodinite v7 Port Configuration: HTTP/HTTPS ports are configured during installation in the Nodinite Portal. The v7 PowerShell installation scripts automatically configure IIS bindings based on your Portal settings.

graph LR subgraph "End-Users" roBrowser[fab:fa-chrome Chrome
fab:fa-firefox Firefox
fab:fa-edge Edge
fab:fa-safari Safari] end subgraph "Web Server" roWebAPI(fal:fa-cloud-sun Web API) roWebClient(fal:fa-globe Web Client) -->|80,443,...| roWebAPI roBrowser -->|80,443,...| roWebClient end

Diagram: End-users access the Web Client from their browsers over HTTP/HTTPS.

Tip

Custom Reporting: The Web Client provides a "Copy API URI" feature that helps users discover Web API endpoints for building custom Reports with PowerBI, Excel, or QlikView. These reporting tools connect directly to the Web API (see Web API Prerequisites for firewall requirements).

Required Firewall Ports

  1. Inbound communication (End-users → Web Client)
    • HTTP and/or HTTPS
  2. Outbound communication (Web Client → Web API)
    • HTTP and/or HTTPS

1. Inbound communication

Port Name Inbound Outbound TCP UDP Comment
80 HTTP default for HTTP
443 HTTPS default for HTTPS

Custom ports (1-65535): Depends on IIS bindings configured in the Nodinite Portal during installation.

Important

If you intend to host Nodinite on non-default ports, contact support for guidance at support@nodinite.com.

2. Outbound communication with the Web API

The Nodinite Web API is responsible for all communication with the underlying databases.

Port Name Inbound Outbound TCP UDP Comment
80 HTTP default for HTTP
443 HTTPS default for HTTPS

Custom ports (1-65535): Depends on IIS bindings for the Web API site.

Note

SQL Server Communication: The Web Client does not directly communicate with SQL Server. All database operations are handled by the Web API, which requires firewall rules documented in the Web API Prerequisites.

Frequently asked questions

Find answers to common problems and the FAQ for the Nodinite Web Client on the Troubleshooting page.

Can I secure the Web Client?

Yes, the Nodinite Web Client fully supports SSL certificates. Add your certificate to IIS and configure the Nodinite Web Client to allow only HTTPS traffic for enhanced security.

Important

Review the Nodinite IIS Hardening user guide for more information.

What SQL Rights does the Web Client require?

None! The Nodinite Web Client does not access any database; the application pool does not need SQL Server grants. This provides a hassle-free, secure experience.

Next Step

Hardening
Install Nodinite
IIS Windows Features

Core Services Package
Web API
Roles
Reports
IIS Authentication settings