Server configuration

There are several configuration files in CloudBeaver.

Main server configuration

The primary configuration file is cloudbeaver.conf. By default, it is placed in the /etc/cloudbeaver/ folder.
But in most cases it is redefined for each server by the command line parameter, -web-config <config-file-path>.
The server configuration is in the JSONC format (JSON with comments and without redundant quotes). It can be parsed by most of the JSON parsers in lenient mode.
Additionally, configuration parameters can be specified in the file workspace/.data/.cloudbeaver.runtime.conf. It is convenient because the workspace can be deployed as a shared docker volume. .cloudbeaver.runtime.conf has the same structure as cloudbeaver.conf. However it has a higher priority than cloudbeaver.conf.

Typical configuration:

{
    server: {
        serverPort: 8978,
        serverHost: "localhost",
        serverName: "CloudBeaver Sample Server",

        // Paths are absolute or relative to the server root folder
        workspaceLocation: "workspace",
        contentRoot: "web",
        driversLocation: "drivers",

        rootURI: "/",
        serviceURI: "/api/",

        // Webapp configuration file
        productConfiguration: "conf/product.conf",

        expireSessionAfterPeriod: 600000,

        develMode: false,

        database: {
            url: "jdbc:h2:${workspace}/.data/cb.h2.dat",
            initialDataConfiguration: "conf/initial-data.conf",
            pool: {
                minIdleConnections: 4, 
                maxIdleConnections: 10,
                maxConnections: 100,
                validationQuery: "SELECT 1"
            }
        }
    },
    app: {
        anonymousAccessAllowed: true,
        anonymousUserRole: "user",
        supportsCustomConnections: false,
        publicCredentialsSaveEnabled: true,
        adminCredentialsSaveEnabled: true,
        resourceManagerEnabled: true,
        resourceQuotas: {
            dataExportFileSizeLimit: 10000000,
            resourceManagerFileSizeLimit: 500000,
            sqlMaxRunningQueries: 100,
            sqlResultSetRowsLimit: 100000,
            sqlResultSetMemoryLimit: 2000000,
            sqlTextPreviewMaxLength: 4096,
            sqlBinaryPreviewMaxLength: 261120
        },
        defaultNavigatorSettings: {
            showSystemObjects: true,
            showUtilityObjects: false,
            showOnlyEntities: false,
            mergeEntities: false,
            hideFolders: false,
            hideSchemas: false
        },
        plugins: {

        },
        enabledAuthProviders: [
            "local"
        ],
        enabledDrivers: [
            
        ],
        disabledDrivers: [
            "sqlite:sqlite_jdbc",
            "h2:h2_embedded"
        ]

    }

}

All paths can be absolute or are relative to the server start directory (or current directory).

Server parameters:

Name	Description
serverPort	Port CloudBeaver server listens on
serverHost	The network interface CloudBeaver server binds to as an IP address or a hostname. If null or 0.0.0.0, then bind network interface to all available interfaces.
serverURL	Server address (full URL). Used to generate links and for third-party services integration.
workspaceLocation	Root folder for projects
contentRoot	Path to directory with static content
driversLocation	Optional path for driver jar files
rootURI	Web application URI prefix. / by default
serviceURI	Services API URI prefix (relative to rootURI). /api/ by default.
productConfiguration	Path to product (web interface) configuration file (json)
develMode	When set to true extra debug, the information is printed in logs and the GraphQL console is enabled on the server.
expireSessionAfterPeriod	Maximum idle time after which the user's session will be closed.

Database configuration

Configures CloudBeaver database where it keeps users, credentials and permission.
In the section server.database:

Name	Description
driver	Database driver (e.g. sqlite, h2_embedded, postgres-jdbc, etc)
url	Database JDBC URL (e.g. jdbc:postgresql://localhost:5432/cb
user	Database user name
password	Database user password
initialDataConfiguration	Path to the initial data file (json) that will be loaded on the first time the server is run

Database connection pool configuration

Configures connection pool to be used by the CloudBeaver database.
In the section server.database.pool:

Name	Description
validationQuery	Query that will check the successful connection to the database
minIdleConnections	Minimum number of idle connections that should be kept in the pool
maxIdleConnections	Maximum number of idle connections that should be kept in the pool
maxConnections	Maximum number of idle and active connections that should be kept in the pool

Database Initial Data

Configures initial data containing administrator credentials and a list of roles and their permission.
Stored in a separate file. The path to which is specified in the server.database.initialDataConfiguration section.

Name	Description
adminName	Username for administrator
adminPassword	Password for administrator
roles	List of initial roles

Roles schema

Name	Description
roleId	Id for the role
name	Name for the role
description	Role description
permissions	Set of available permissions for the role

Configuration example:

{
    adminName: "cbadmin",
    adminPassword: "cbadmin20",
    roles: [
        {
            roleId: "admin",
            name: "Admin",
            description: "Administrative access. Has total and full authority.",
            permission: ["public", "admin"]
        },
        {
            roleId: "user",
            name: "User",
            description: "Standard user",
            permission: ["public"]
        }
    ]
}

Application parameters:

In the section app:

Name	Description
anonymousAccessEnabled	Allows anonymous access. Anonymous users have a role anonymousUserRole.
anonymousUserRole	A role that will be assigned to the anonymous user, user by default.
authenticationEnabled	Enables users' authentication. If disabled, then only anonymous access is allowed.
supportsCustomConnections	Allows users to create custom connections to any databases. Otherwise only the CB administrator can create/edit connections.
publicCredentialsSaveEnabled	Allows you to save user database credentials in a local cache.
adminCredentialsSaveEnabled	Allows you to save global database credentials in a local cache.
redirectOnFederatedAuth	If there is only one federation authentication configuration, then login attempt will automatically be made when the application is opened.
forwardProxy	Identifies the originating IP address and other headers of a client connecting to a web server through an HTTP proxy.
enabledDrivers	List of drivers that are allowed to be used. If the list is empty, all drivers are allowed.
disabledDrivers	List of drivers that are prohibited for use. If the list is empty, all drivers are allowed.
enableReverseProxyAuth	Enabling reverse proxy authorization mechanism for more details can be found here.
defaultAuthProvider	The provider that will be used for authorization by default.
enabledAuthProviders	List of allowed authorization providers. If the property is absent, all providers are allowed.
defaultNavigatorSettings	Default database navigator settings.

Resource quotas

You can configure the following resource quotes in the section app.resourceQuotas:

Name	Description
dataExportFileSizeLimit	Maximum file size for data export operation (in bytes)
resourceManagerFileSizeLimit	Maximum file size saved in the resource manager (in bytes)
sqlMaxRunningQueries	Maximum number of simultaneous queries for a single user session. Includes data read queries (i.e. table data view)
sqlResultSetRowsLimit	Maximum number of rows to select from a table or query
sqlTextPreviewMaxLength	Maximum size for text file shown in value panel (in bytes)
sqlQueryTimeout	Maximum time (in seconds) for SQL query execution (including table data read)
sqlBinaryPreviewMaxLength	Maximum size for binary file (also affects JSON in the SQLite) shown in value panel (in bytes)

Navigator settings

You can configure the following properties in the section app.defaultNavigatorSettings:

Name	Description
showSystemObjects	Show system objects.
showUtilityObjects	Show "utility" objects.
showOnlyEntities	Only show schemas and tables.
mergeEntities	Show all types of database objects in one list (tables, sequences, etc.).
hideFolders	Hide folders like "Tables", "Schemas", "Columns", etc.
hideSchemas	Do not show schemas (all tables in one list).

Simple view mode properties example:

    defaultNavigatorSettings: {
        showOnlyEntities: true,
        hideFolders: true,
        hideVirtualModel: true
    }

Automatic server configuration

When you start the CloudBeaver server for the first time you will see the administrator interface for server configuration.
In some cases the server must be configured automatically (e.g. when it is run in the Kubernetes environment).
The following parameters must be specified in the configuration:

Name	Description	Example
CB_SERVER_NAME	Server name	Test Server
CB_SERVER_URL	Server base URL	https://cloudbeaver.domain.com:10000/
CB_ADMIN_NAME	Administrator user name	admin
CB_ADMIN_PASSWORD	Administrator user password	S0mePazzworD

These parameters can be specified in:

• OS environment variables
• configuration file .cloudbeaver.auto.conf which must be placed in the same location as the cloudbeaver.conf file.

Datasources configuration

You can find a detailed description at here

Using environment variables

You can use references on environment variables in most server configuration properties. For example:

{
    server: {
        serverPort: ${cb.port},
        serverHost: "${cb.host}",
        serverName: "CloudBeaver Server",

        rootURI: "${cb.prefix}",
        serviceURI: "/api/",

        expireSessionAfterPeriod: ${cb.expire-time},
    }
}