What is the Nodinite Web Client?

The Nodinite Web Client is the browser-based user interface of Nodinite. Business users, operators, and administrators use it to search Log Views, work with Monitor Views, explore the Repository Model, and administer the platform. The Web Client is part of the Core Services package and talks only to the Web API; it never reads a database itself.

This page explains how the Web Client is built and hosted, how users sign in, and which System Parameters change what the Web Client shows. For day-to-day use, see the end-user guide Getting Started with Nodinite.

Understanding the Web Client Architecture

The Web Client runs in the browser and communicates only with the Web API. All data access, business logic, and security enforcement happen server-side.

Architecture Components

Note

The Web Client is a single-page application (SPA): it loads once and then calls the Web API in the background. This keeps the user experience responsive and reduces server load.

Performance and Usability

• Single-page application – fast, responsive UI with few full page loads
• Paged results – large result sets are fetched page by page
• Responsive design – adapts to desktop, tablet, and mobile layouts
• Export – copy the API URI, print, or export Log View results to CSV (see Copy API, Print, and Export to CSV)

Hosting in Nodinite v7

In Nodinite v7 on Windows Server, each Core Service is its own IIS web site on its own port; the container runtimes run each service as a container instead. You don't create or edit the Web Client site by hand; the Nodinite Portal collects the values and the generated CLI package creates the site.

The Web Client is served at the root of its site, for example https://nodinite.contoso.com:<port>/. See Install Nodinite v7 for the complete flow, and Prerequisites for what the server, the browser, and the firewall need.

Supported Client Browsers

End-users need a modern, HTML5-compatible browser. The Web Client is tested and supported on:

Important

Internet Explorer is not supported. Use a modern browser.

Some features, such as downloading message payloads and exports, open a new window; see Allow browser pop-ups.

Authentication and Authorization

Each environment uses one authentication mode, chosen in the Portal Step 2: Auth. The installer configures the Web Client site to match.

Tip

For the Microsoft Entra ID app registrations, see Install Nodinite v7 - OpenID - EntraID. When users get an unexpected login prompt with Windows Authentication, see Login prompt asks for a password.

Both modes enforce role-based access control (RBAC) with Roles: users only see the data and features their Roles allow.

Windows Authentication Flow

1. The browser sends a Kerberos ticket (or an NTLM response) to IIS.
2. IIS validates the credentials against Active Directory.
3. The Web API receives the authenticated Windows identity.
4. The Web API looks up the User and Role assignments in the Configuration Database.

OpenID Connect Flow

1. The browser redirects to the identity provider, for example Microsoft Entra ID.
2. The user signs in with the identity provider (including MFA when required).
3. The identity provider redirects back to the Web Client.
4. The Web Client obtains tokens and calls the Web API with an access token.
5. The Web API validates the token and maps its claims to Roles through Claims and Policies.

Authorization Model

Important

Defense in depth: Even if UI authorization is bypassed, for example by crafting API calls, the Web API enforces permissions.

For Role configuration and permission sets, see Roles, Permission Set for Log Views, and Access Management.

System Parameters that Shape the Web Client

The Web Client reads more System Parameters than any other component. Values are stored in the Configuration Database and changed under Administration › Settings › System Parameters (see Manage System Parameters). No restart is needed; the Web Client picks up a new value within about 15 seconds (HideAdditionalFieldValuesInLogViews is cached for up to an hour).

Appearance

• EnvironmentName – the environment name shown in the header (see Menu - Environment)
• EnvironmentColor – the colour of the header bar, per environment

Log View Data Protection

These parameters apply in every Log View, on top of the Permission Set for Log Views:

• HideSearchFieldValuesInLogViews – hides Search Field values that are not part of the Log View
• HideAdditionalFieldValuesInLogViews – shows, hides, or masks built-in Log Event detail fields
• ProtectedContextValues – masks the values of named context properties (Context Options)

Repair and Resend

• AllowResubmit – master switch for Resend from Log Views
• AllowRepair – enables Repair and resubmit (needs AllowResubmit)
• ResendWebhookSettings – the Webhooks users can pick as a resend target
• ResubmitContextValuesForActiveMQ – context properties sent along when resubmitting to ActiveMQ

AI

• AI – feature flags for the AI Assistant and other AI features in the Web Client (see AI Overview)

Content and Repository

• ReservedArticleTagNames – tags never copied onto a new Snippet in Articles
• StylesheetScriptsEnabled – allows embedded scripts in Stylesheets
• SharedFilePolicy – allowed upload types and link behaviour in the File Library
• DashboardPluginSettings – the sandbox for Custom Dashboard Items
• DisableCustomFields – hides the legacy Custom Fields menus
• UseContracts – turns the Contracts entity on or off
• MessageProcessingMaxBodySize – the Web Client flags Message Types whose recent bodies exceed the limit

Access

• DefaultRolesInViews – Roles pre-selected when an administrator creates a new view
• UseActiveDirectoryGroups – turns Windows AD Groups on or off

Licence and Version

These are 🔒 read-only in System Parameters:

• ProductKey – the licence key (change it in Manage License)
• CustomerName – the licensee name, paired with the ProductKey
• Version – the installed version, shown in Menu - Version

What Users Do in the Web Client

While this page focuses on the technical side, end-users work with these features in the Web Client:

• Dashboard – integration health at a glance
• Log Views – search transactions across systems with business-friendly filters
• Monitor Views – track system health, receive alerts, and run remote actions
• Repository Model – the integration landscape as living documentation
• Business Process Models – end-to-end workflows with operational status
• Administration – users, roles, views, and settings (administrators only)

Everything the Web Client does goes through the Web API, so you can automate the same operations with the REST API.

Note

Nodinite v6 is no longer supported. To move an existing v6 installation, follow Updating from v6 to v7.

Next Steps

• Getting Started with Nodinite – end-user guide to the Web Client
• Prerequisites – server, browser, and firewall requirements
• Install the Web Client – what you set in the Portal and how to verify
• Manage System Parameters
• Access Management – Roles, Users, and security
• Troubleshooting

Related Topics

• Core Services
• Web API
• Configuration Database
• Log Databases
• Update the Web Client
• Uninstall the Web Client
• System Parameters
• Roles
• Users
• Windows AD Groups
• Claims
• Policies
• Log Audits
• HTTP SPN for IIS
• NTLM vs Kerberos Authentication
• How to perform hardening on your Nodinite installation