Anjana Data Platform natively includes an internal authentication mechanism based on a database. On the login screen it usually appears as "Provider: Database", since user credentials are stored and managed in the internal Anjana Data Platform database, along with the platform's authorization configuration.
This provider allows managing users and passwords directly from the Configuration Panel, without needing to integrate an external provider.
Integration model
Authentication
Database authentication is embedded in the Zeus authentication microservice.
Its activation and configuration is done through the configuration file of that microservice.
For more information about managing/creating users in this provider, refer to the configuration documentation for Governance Operational Model.
Configuration of the Database provider
The authentication providers active on the Platform are declared in the security.authentication property.
To enable the internal provider (Database), configure:
security:
authentication:
db:
# Habilita o deshabilita la autentificación por base de datos
enable: true
Informational note
Activation of the Database provider is applied at the Zeus microservice configuration level.
Therefore, after modifying the security.authentication.db.enable property, it is necessary to restart the Zeus microservice for the change to take effect on the login screen and in the authentication flow.
Disabling the Database provider
In some environments, once the setup is complete and an external provider (AWS IAM, EntraID, Google IAM, etc.) has been integrated, customers request disabling the internal Database provider to force access only through the corporate provider.
To do this, simply deactivate the DB provider in the Zeus configuration:
security:
authentication:
db:
# Deshabilita la autenticación interna por base de datos
enable: false
Informational note
Deactivation of the Database provider is applied at the Zeus microservice configuration level.
Therefore, after modifying the security.authentication.db.enable property, it is necessary to restart the Zeus microservice for the change to take effect on the login screen and in the authentication flow.
Required credentials
Required credentials
No additional credentials need to be configured for this provider.
Internal authentication uses the same database access credentials that are already defined for the correct operation of the Zeus microservice.
Important considerations
-
When disabling Database, no user will be able to authenticate with internal credentials from the login screen.
-
Make sure that at least one external provider is enabled and operational before applying the change, to avoid blocking access to the platform.
-
This change only affects authentication. Existing internal users can still be defined in the database to configure authorization, but they cannot be used to log in while Database is disabled.