- 2 minutes to read
Step 4: Configure Authentication
Choose the primary sign-in model for the new Nodinite Environment. The Portal stores these values so the installation script can configure the Web Client, Web API, and related services correctly.
Authentication Options
| Option | Best fit |
|---|---|
| Windows Authentication | On-premises environments integrated with Active Directory |
| OAuth 2.0 / OIDC | Environments using modern identity providers and OpenID Connect |
Configure Windows Authentication
Windows Authentication is the default for most Windows Server installations.
| Mandatory | Variable | Default | Description |
|---|---|---|---|
| Authentication Method | Windows |
Uses Active Directory and integrated security | |
| Default Domain Name | <DomainName> |
Domain prefix for account names | |
| Admin Account | <NodiniteAdminUsrAccountName> |
Initial administrator account | |
| Default Services Account Name | <DefaultServiceAccountName> |
Base account used by the services unless overridden |
Example of the Authentication tab with Windows Authentication selected in the Portal.
Example of the Default Domain Name field used when Windows Authentication is selected.
Configure OAuth 2.0 / OIDC
Use the OpenID Connect installation guide when the Environment will authenticate through an external identity provider.
- OAuth 2.0 / OIDC requires TLS.
- Prepare the identity provider settings before running the installation script.
- Continue with Install Nodinite v7 - OpenID for the detailed mapping.
Decision Notes
- If you are building a classic on-premises installation, Windows Authentication is usually the fastest route.
- If you choose OAuth 2.0 / OIDC, do not postpone TLS. Configure it in Step 5 before you download binaries.