DBeaver includes support for LDAP Mechanism authentication, an additional secure method to connect to your Teradata databases.

To configure LDAP Mechanism authentication in DBeaver, follow these steps:

1. From the Authentication dropdown menu, select the LDAP Mechanism method.

2. In the Username and Password fields, enter the credentials associated with your LDAP server.

3. Enter the necessary additional information in the LDAP Extra DATA field. This might be specific configurations or parameters required by your LDAP server. Consult with your system administrator or refer to Teradata’s LDAP documentation for the exact details.

Tip: Selecting the Save credentials locally option means you will not have to input your credentials every time you connect.

4. After entering your credentials and extra data, click the Test Connection button. If all settings are correctly configured, DBeaver will connect to your database using the LDAP Mechanism authentication method.

Note: This feature is available in Lite, Enterprise, Ultimate and Team editions only.

DBeaver comes with Microsoft Entra ID (formerly Azure AD) authentication support, allowing secure access to your databases. This article assumes that you are already registered with Microsoft Azure.

You can find detailed information about Entra’s features and capabilities in the official Entra documentation.

To properly configure Azure Entra ID authentication in DBeaver, fill out the credential fields detailed in our guide.

Note: If you belong to an Azure Entra ID Group, you must add the AD Group name to your Connection configuration. This step, possibly requiring admin assistance, involves right-clicking on your database in the Database Navigator and selecting Edit Connection. In the ensuing dialog, navigate to the Connection Settings tab and input your AD Group name in the designated field.

Note: This feature is available in Lite, Enterprise, Ultimate and Team editions only.

DBeaver is fully compatible with the MongoDB authentication method, offering you a secure way to access your MongoDB databases.

Here are the steps to configure MongoDB authentication:

1. From the Authentication dropdown menu, select the MongoDB authentication method.

2. From the Mechanism dropdown menu, select an option. The following table outlines the available authentication mechanisms:

You can read more about these mechanisms on the MongoDB documentation page.

3. Fill in the Source field if necessary.

4. Enter the username and password in the Username and Password fields respectively.

   Tip: If you check the Save credentials locally option, you will not be asked to input your credentials every time you connect.

5. Once you have input your credentials, click the Test Connection button to verify your settings. If everything is configured correctly, DBeaver should now be able to connect to your database using the MongoDB authentication method.

This guide describes how to manage/secure the DBeaver database connections. It is designed for System administrators. Regular users should check this guide.

DBeaver keeps connections information in the project folder. By default, all projects reside in the workspace.
The default project folder is workspace\workspace6\General.

DBeaver up to 6.1.3
DBeaver keeps information about project connections in the

DBeaver can load multiple connection files. Any files in the project folder matching the

DBeaver < 6.1.3 (Legacy)
DBeaver keeps information about project connections in the

DBeaver can load multiple connection files. Any files in the project folder matching the

You can import a connection from CSV or XML files.

The CSV file must have a header row (first line of file) with column names (see list of supported columns below). The XML file should contain a top-level element and a set of nested elements. The connections config must be specified in the attributes of the nested elements. Attribute names are the same as the CSV column names.

You can only specify the URL or the host/port/etc setting.
User name/password are optional.

name,host,port,server,database,url,user,password,type

Postgre Import XML 1,localhost,5432,,postgres,jdbc:postgresql://localhost:5432/postgres,postgres,postgres,dev

Postgre Import XML 2,localhost,5432,,postgres2,jdbc:postgresql://localhost:5432/postgres2,postgres2,postgres2,prod

<connections>

    <connection name="Postgre Import XML 1" host="localhost" port="5432" server="" database="postgres" url="jdbc:postgresql://localhost:5432/postgres" user="postgres" password="postgres" type="dev" />

    <connection name="Postgre Import XML 2" host="localhost" port="5432" server="" database="postgres" url="jdbc:postgresql://localhost:5432/postgres2" user="postgres2" password="postgres2" type="prod" />

</connections>

It is possible to set the connection settings as read-only (protected by password)

• Generate MD5 hash of your password. You can do it from the command line using Linux utility md5sum (
  md5sum &lt;&lt;&lt;"your password"
  ) or you can do it online – just google “MD5 hash online”.
• Add field
  lockPassword
  in the connection descriptor (in
  .dbeaver/data-sources.json
  in
  connections
  element. So it will look like this:

"postgres-jdbc-161537836e8-3e0957d039995715": {

   "provider": "postgresql",

   "driver": "postgres-jdbc",

   "name": "PostgreSQL - postgres",

   "save-password": true,

   "show-system-objects": true,

   "read-only": false,

   "folder": "PG",

   "lockPassword": "2ba81a47c5512d9e23c435c1f29373cb"

...

}

• If the user will try to change connection settings now, he/she will be asked for a password.

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

"postgres-jdbc-161537836e8-3e0957d039995715": {

   "provider": "postgresql",

   "driver": "postgres-jdbc",

   "name": "PostgreSQL - postgres",

   "user": "${dbeaver.default-user}",

...

}

You can customize drivers configuration in the workspace/.metadata/.plugins/org.jkiss.dbeaver.core/drivers.xml file. If you have some pre-installed jar files you can reference them in drivers.xml. Example:

<library type="jar" path="absolute-jar-folder-path\driver-jar.jar" custom="true" />

Also in drivers.xml you can use the following variables to specify relative paths:

For instance:

<library type="jar" path="${workspace}\drivers\my-driver.jar" custom="true" />

Full drivers.xml example:

<?xml version="1.0" encoding="UTF-8"?>

<drivers>



    <provider id="postgresql">

        <driver id="postgres-jdbc" custom="false" embedded="false" name="PostgreSQL" class="org.postgresql.Driver" url="jdbc:postgresql://{host}[:{port}]/[{database}]" port="5432" description="PostgreSQL standard driver">

            <library type="jar" path="maven:/org.postgresql:postgresql:RELEASE" custom="false" version="42.2.20">

                <file id="org.postgresql:postgresql" version="42.2.20" path="${drivers_home}/maven/maven-central/org.postgresql/postgresql-42.2.20.jar" />

            </library>

            <library type="jar" path="maven:/net.postgis:postgis-jdbc:RELEASE" custom="false" version="2.5.0">

                <file id="net.postgis:postgis-jdbc" version="2.5.0" path="${drivers_home}/maven/maven-central/net.postgis/postgis-jdbc-2.5.0.jar" />

            </library>

            <library type="jar" path="maven:/net.postgis:postgis-jdbc-jtsparser:RELEASE" custom="false" version="2.5.0">

                <file id="net.postgis:postgis-jdbc-jtsparser" version="2.5.0" path="${drivers_home}/maven/maven-central/net.postgis/postgis-jdbc-jtsparser-2.5.0.jar" />

            </library>

        </driver>

    </provider>

    

</drivers>

In some cases you may need to provide a driver’s configuration or driver

This can be done by adding a special parameter in the

Tip: Detailed instructions on finding

dbeaver.ini

are available in our article.

This file has the same structure as

You can specify partial driver configuration. For example if you need to configure only the jar path then it may look like this:

<?xml version="1.0" encoding="UTF-8"?>

<drivers>

  <provider id="generic">

    <driver id="netezza">

      <library type="lib" path="X:\jdbc-drivers\netezza-jdbc.jar" />

    </driver>

  </provider>

</drivers>

This guide describes how to set up an application preferences through configuration files without even booting it up.

Preference files have the extension

You might not find a preference file you are interested in, if it has not been created yet. In this case, you will need to create one yourself. See the examples below to figure out which preference file you need.

You can easily import and export your workspace configuration. Follow the steps below to perform these actions:

1. Go to File -> Import (for importing) or Export (for exporting).
   
2. In the opened window, select DBeaver, then choose Preferences from the nested menu.
   

3. In the new window:
   

   • For importing, navigate to the location where the configuration file is stored, select the file, and click Finish.
   • For exporting, choose the destination where you want to save the configuration file, and click Finish.
     

4. If you are importing, DBeaver will prompt you to restart the application to apply the changes. Confirm the restart to complete the import process.

Preference files consist of key-value pairs glued together with

# file org.jkiss.dbeaver.test.prefs

some.key=value1

some.other.key=value2

You can place the following preferences in the

For more information, please see Simple and Advanced View.

The preferences of GIS Viewer from Data Editor you can find in the

This guide outlines the steps for enhancing security and control in DBeaver by restricting specific functionalities.

For Windows, Mac, and Linux, restrictions in the

Tip: Detailed instructions on finding

dbeaver.ini

are available in our article.

Follow the appropriate steps based on your operating system and preference.

1. Navigate to the directory containing the
   dbeaver.ini
   file.
2. Use a text editor to open the configuration file.
3. Locate the
   -vmargs
   line within the file.
4. Add the desired settings from the Configuration options, ensuring each setting is preceded by
   -D
   (for instance
   -Dpolicy.data.export.disabled = true
   ) and placed below the
   -vmargs
   line.
5. Save the edited file.
6. Restart DBeaver to apply changes.

1. Open the Registry Editor by typing
   regedit
   in the Run dialog (Win + R).
2. Navigate to the following path in the Registry:
   HKEY_CURRENT_USER\Software\DBeaver Corp\DBeaver\policy
3. Create a new value for each setting, from the Configuration options based on desired restrictions.
4. Exit the Registry Editor and restart DBeaver to apply the changes.

Important: Editing the Windows Registry can significantly affect your system. Always make sure to back up the registry before making any changes. For more information on how to work with the Windows Registry, refer to the Microsoft Documentation on Registry Editing.

This section consolidates the configuration options, applicable through Windows Registry keys and as settings in the DBeaver configuration file.

This section outlines the parameters that can be configured either through the Windows Registry or directly in the

This section details the parameters that can be set only in the

DBeaver offers you the ability to use most of its features with a keyboard and screen readers. Here you will find a guidelines on how to use DBeaver without a mouse in some common cases.

Note: DBeaver is tested primarily with standard Windows keyboard shortcuts for accessibility.

DBeaver provides support for various screen readers:

• NVDA. Find more details in the NVDA User Guide.
• JAWS. Access comprehensive information through the JAWS Documentation.
• Narrator. More information available at the Narrator User Guide.

To change the screen reader in DBeaver, navigate to Window -> Preferences -> User Interface -> Accessibility.

DBeaver is an application consisting of many parts, so-called Views, such as Database Navigator, SQL Editor, Data Editor, etc. A Toolbar with many buttons inside each View and horizontal and vertical tabs allows you to switch between Views and inside them.

Main navigation shortcuts

• You can switch Views by using Ctrl+F7 | ⌘F7.
• You can switch between buttons on the toolbars and menus using Tab and the arrows.

How to switch tabs

• You can switch horizontal tabs by using Ctrl+PageUp/PageDown.
• Sub-tabs can be switched by using Alt+PageUp/PageDown.
• If there are vertical tabs inside the view, you can switch them by using Ctrl+Alt+PageUp/PageDown or Ctrl+Shift+PageUp/PageDown.

When you focus on any interface object, such as a table, column, tab, or cell, you can open the Context menu to see all the actions available for that object.

To open the Context menu, use Shift + F10 | ⇧F10.

Most of DBeaver’s functions are accessible through special shortcuts. You can find them in Window -> Preferences –> User Interface –> Keys. If you mostly use the keyboard, you can switch to the DBeaver Keyboard Only scheme, which has additional shortcuts.

Learn more about DBeaver shortcuts

Themes: DBeaver supports theme customization to enhance your user experience. Among the available options, DBeaver provides integration for the High-Contrast theme native to Windows systems. For more details on this and other themes, see our comprehensive theme guide.

Fonts: To change fonts in DBeaver, navigate to Window -> Preferences –> User Interface —> Appearance —> Color and fonts, and open DBeaver fonts. The Main font allows you to change the font family, size, and color in most elements of DBeaver’s interface, including the Database Navigator and the Data Grid. The Monospace font changes the font in the SQL Editor and other Views with monospaced fonts.

Data Colorization: You can color rows in the Data Grid by following some rules or even by selecting colors for particular data types.

Let’s see some comments on using the most popular Views in DBeaver with the keyboard and screen reader.

In the Database Navigator, you can view and open all the database connections and objects inside them. You can move between database objects and open nodes using arrows.

• To view object properties, use F4.
• To open SQL Editor associated with the selected object, use F3.

See all Database Navigator shortcuts

To create a new connection, open the Wizard window using Ctrl+N | ⌘N, then type connect and select Database connection.

See Connection shortcuts

The Properties Editor is used to see all the information about database objects. When you focus on the first row of the table, NVDA reads the contents of the row with the corresponding column names.

• You can open object properties with F4.
• To switch between left-side tabs, use Alt+Shift+Up | Alt+Shift+Down.

See Properties Editor shortcuts

The SQL Editor allows you to create and execute SQL scripts associated with a database connection. To open the SQL Editor, focus on the connection or table in the Database Navigator and press F3. To execute the SQL script under the cursor, press Ctrl+Enter.

• See SQL Editor shortcuts

When you place your focus on the first cell in the data table, the NVDA screen reader says the table name and the name of a column consisting of this cell. If you move from one cell to another, the screen reader announces the column names when you change focus.

If you need to work with columns using the keyboard, you can select an entire column, copy the column name, and resize the column using special keyboard shortcuts. Some of them are only available in the DBeaver Keyboard Only scheme.

See Result Set shortcuts

ER Diagrams are fully accessible with the keyboard and the NVDA screen reader. You can move inside the table, move or resize it, and listen to the screen reader pronounce the table name and column names inside that table.

Learn more about ER Diagram shortcuts

Note: This driver is available in Lite, Enterprise, Ultimate and Team editions only.

AWS DocumentDB is based on the MongoDB engine.
It has several minor differences in the query processing and network configuration.
However, most features which work for MongoDB will work for DocumentDB as well. Please refer to the MongoDB article.

AWS restricts direct access to DocumentDB clusters from outside of the cloud (region). So you can connect to it directly (using a cluster host name) only when DBeaver is deployed on the EC2 instance.

In other cases you will need to use the SSH tunnel through a proxy machine to access DocumentDB instance. Please read the AWS Documentation about proxy configurations: https://docs.aws.amazon.com/documentdb/latest/developerguide/connect-from-outside-a-vpc.html

In DBeaver you can use the SSH tab on the connection settings page. Just enter proxy host, user name and specify a private key file (it is provided by AWS as a keypair).

DBeaver processes DocDB SQL queries exactly like in MongoDB. It supports SELECT, UPDATE, INSERT and DELETE queries.
SELECT queries support WHERE, ORDER BY, GROUP BY and HAVING clauses.

DocumentDB restricts the