Security
Security by Design
Traditional security breaks because it relies on developers remembering to add permission checks at every API endpoint and controller. We eliminate this risk by enforcing security directly into the Kodall Engine. Zero Trust and Least Privilege are enforced by default making security an immutable property of the platform.
In Kodall, security is embedded into the Foundation, directly above Data Modeling. The moment you define a business object in the Development Module, its access policies automatically propagate across every tier of the platform: database queries, logic workflows, REST APIs, and UI views.
All security requests have a single entry point into the kernel, so bypassing authorization checks is structurally impossible.
Identity
Core Authenticator
Identity management is orchestrated centrally out of the box through native Keycloak integration. Kodall validates user identity at the perimeter before any request reaches application logic.
Supported Providers
The platform syncs seamlessly with existing enterprise identity providers via OpenID Connect (OIDC), Active Directory, LDAP, or SAML 2.0. This ensures corporate user hierarchies, multi-factor authentication policies, and SSO apply universally.
Data Horizons
Data access goes beyond simple page-level permissions. Kodall combines dynamic Role-Based Access Control (RBAC) with row-level security mapped directly to your corporate structure. Company records reflect real-world hierarchies: Organizations, Business Units, and Asset Owners.
When a user requests data, the Java kernel evaluates their assigned role and dynamically injects row filters into the database call based on their explicit data horizon. Unauthorized records are masked at the database abstraction layer before payload construction:
| Scope Horizon | Access Boundary | Operational Context |
|---|---|---|
| All | Global platform-wide visibility | System administrators and compliance auditors |
| Organization | Parent enterprise entity boundaries | Executive leadership across subsidiaries |
| Business Unit | Departmental or regional team scope | Department managers (e.g., Sales EU, HR) |
| Owner | Restricted strictly to records created by or assigned to the user | Individual task queues and personal assignments |
Execution Pipeline
To guarantee Zero Trust, every inbound action follows an identical execution path inside the kernel:
Perimeter Auth
Keycloak validates token signature and active session.
RBAC Evaluation
The kernel checks if the user's role permits the action on the business object.
Data Horizon Injection
The database abstraction layer injects Row-Level Security constraints (Owner, Business Unit, etc.) directly into the generated SQL query.
Kernel Audit Logging
A tamper-proof audit log records user ID, timestamp, and field deltas directly from the kernel runtime.