Authentication. You can use new authentication providers — NTLM, Okta, AWS OpenId – to log in to web and desktop applications, making the following types of authorization available: AWS SAML, AWS OpenId, AzureAD, Google, NTLM, Okta OpenId, OpenId, SAML.
User provisioning. You can import users from yourAzureAD and Okta business accounts.
Integration with the Git version control system was implemented. User can keep project scripts, diagrams, datasets, connection configurations, bookmarks, and other data in a Git repository.
Task scheduling has been significantly improved: tasks run on the server, and the user can retrieve export result files in the desktop application.
Synchronization work better, and users receive notifications in the desktop application, when creating or deleting projects and connection folders. Configuration changes are also synchronized.
Azure Cosmos DB
AWS Timestream (added to Cloud Explorer)
Crate DB for Postgres
Kafka (available in Ultimate Edition)
Materialize (only in desktop)
Salesforce (JDBC driver created by DBeaver team)
Security: SQLite driver version was updated due to the found vulnerability CVE-2023-3269.
Traditional Chinese, Chinese Simplified, German, and Portuguese translations are improved;
Users can select Portuguese as the default language during installation.
DBeaver Team Edition desktop
Tableau integration: you can connect to Tableau to edit Tableau custom queries in the desktop interface.
Now you can connect to a database using Kubernetes proxy. To configure it, click the ‘Network configuration‘ button in the connection dialog.
ODBC driver became more stable. It supports any database with the available ODBC driver, the most popular once being Amazon Redshift, BigQuery, DB2, DB2 for IBMi, MariaDB, MySQL, Oracle, PostgreSQL, Snowflake, SQLite, and SQL Server.
Spatial data presentation is enhanced: you can copy coordinates, viewport bounds, and selection. You can also view PostGIS data and labels on the map.
Users can see chart presentations for non-numeric values, for example, for salary or grades.
Connection dialog now supports screen readers.
JAWS and Narrator support was improved for Data Editor and vertical tabs.
High contrast theme support was significantly improved. You can choose a high contrast theme in your OS, and the DBeaver high contrast theme is enabled.
Certificate management was added: you can find CA certificates used for SSL access in the Trust store section in Preferences or import your own certificate.
Project and user password security was improved.
We have improved the security of storing user settings.
Google BigQuery: DDL for storage procedure is available.
Greenplum 7.0 is now supported.
Oracle: XML presentation is supported.
PostgreSQL: Debugger was improved: we fixed many significant bugs and enhanced the performance.
Vertica: Stored procedures are supported, you can view and execute them. Execution plan is available, including JSON queries.
DBeaver Team Edition web
Performance: Pagination has been added to the Navigation tree and metadata viewer, allowing users to work with a larger number of database items;
Navigation tree: Filters for the Navigation tree allow hiding and showing schemas within the interface;
Access Management: The ability to unlink SSO credentials from user has been implemented;
Authentification: The SSL option is available for establishing connections in MySQL, PostgreSQL, Clickhouse, Mongo, Cassandra;
Connections: Connections can be pre-configured into the workspace in the Global Configuration JSON file and then displayed in the interface;
The ability to rearrange columns in the Data Editor has been added;
The ability to use custom functions in the Grouping panel has been added;
SQL Editor: Users can simultaneously edit resources, allowing them to work together;
Driver management: Custom settings have been added to the interface for the following dialogue connections: SQLite, DB2, SQL Server, MySQL, Oracle and PostgreSQL;
Password autofill functionality has been removed;
The ‘eye‘ icon for password fields has been removed – the passwords entered into fields will not be displayed in the interface;