Skip to content

Authentication Configuration

Overview

The Authentication tab of the application configuration controls whether users must authenticate before accessing the application. It also provides a set of mocked user accounts used during development to simulate different user identities and scopes.

For detailed documentation on how authentication and authorization work in Bellini — including public and private pages, scopes, and runtime access control — see the Authentication & Authorization section.

What You Will Learn

  • How to enable or disable authentication for a Bellini application
  • What mocked user accounts are and how they are used during development
  • How to configure mocked users with different identities and scopes

When To Use This

Use this tab when:

  • You want to require users to log in before accessing the application.
  • You need to test your application with different user identities or scopes during development.

Enabling Application Authentication

The Enable Authentication checkbox controls whether authentication is required to access the application.

  • Checked — users must authenticate via Lonti SSO before accessing the application and any of its secured APIs. Once the application is deployed, user access can be managed in the Lonti Console.
  • Unchecked — the application is publicly accessible without authentication.

Mocked User Accounts for Development

The For Development section contains a table of Mocked User Accounts. These accounts simulate end-users during development and are only active in the development environment — they are not used in deployed applications.

Mocked accounts are useful when your application has UI behaviors that depend on the authenticated user, such as showing different content or features based on a user's assigned scopes (e.g. an admin scope that reveals an administration panel).

Each row in the table represents a simulated user with the following fields:

Field Description
Full Name The display name of the mocked user.
Email The email address of the mocked user, used as their identity.
Enabled Whether this mocked account is active and available for use during development.
Scopes The scopes assigned to this user, used to simulate different permission levels.

Helpful Resources