Skip to main content
Version: 3.2

No Authentication

warning

This configuration is inherently insecure. It is intended for demos, trials, initial setup, and verification only. Do not use this in production.

When set to none, Cortex signs every visitor in as the account specified by the OverrideUsername setting and grants access to every Business Object and record.

Configuration​

In appsettings.json, set the Authentication section as follows, and specify the account to authenticate as with OverrideUsername:

{
  "Authentication": {
    "Type": "none",
    "OverrideUsername": "yourUsernameHere"
  }
}

If you prefer environment variables, set:

  • Authentication:Type on Windows
  • Authentication__Type on Linux
  • Authentication:OverrideUsername on Windows
  • Authentication__OverrideUsername on Linux

Specifying the Account to Authenticate As​

none mode does not use a fixed built-in account. You choose which account is impersonated by setting OverrideUsername to the username of an existing Cortex user. That user's permissions and security group determine what visitors can see and do.

For example, to authenticate as the built-in administrator account:

{
  "Authentication": {
    "Type": "none",
    "OverrideUsername": "cortex.admin"
  }
}

If OverrideUsername is left empty, Cortex falls back to the built-in administrator account (cortex.admin).