OneDB v.3.2.0

Release Date: July 2026
Release Type: Feature and Security Enhancement Release
Branch: 3.2.0

Overview

OneDB v3.2.0 introduces initial IBM Db2 support across database connectivity, metadata discovery, Field Settings, group permissions, and the read-only Database Browser.

This release enables administrators to connect OneDB to Db2 databases, discover authorized database objects, configure field-level masking or tokenization, and securely view protected Db2 records through the OneDB Management Console.

The release also improves the Database Migration wizard by adding searchable Source Connection and Target Connection selectors.

What’s New

IBM Db2 Database Connectivity

OneDB now supports authenticated connections to IBM Db2 databases using the IBM Data Server Driver for JDBC and SQLJ.

Db2 connection validation verifies database connectivity and authentication while presenting sanitized messages for authentication failures, connection errors, and timeouts.

The database name is displayed as Db2 in the OneDB user interface, while DB2 remains the internal and persisted database type value.

Permission – Aware Db2 Metadata Discovery

OneDB can discover the following Db2 database metadata:

  • Schemas
  • Tables
  • Views
  • Columns
  • Primary keys

Db2 system schemas are excluded from normal metadata browsing.

OneDB performs additional read-access validation before displaying Db2 objects. This prevents inaccessible schemas, tables, views, and columns from being exposed through the user interface or manually crafted requests.

Db2 Field Settings

Field Settings now supports Db2 database objects using a schema-aware field identity.

Administrators can discover authorized Db2 columns and configure masking or tokenization protection for selected fields.

Supported Field Settings operations include:

  • Creating field protection settings
  • Saving and reloading settings
  • Editing existing settings
  • Deleting field settings
  • Validating database, schema, table, view, and column access

Server-side validation prevents protection rules from being created for inaccessible, nonexistent, or invalid Db2 objects.

Db2 Group Permissions and Field Access

Db2 is now integrated with OneDB group permissions and Group Field Access configuration.

Db2 field permissions use both the database and schema identity, allowing OneDB to correctly distinguish objects with the same table or column name across different schemas.

Db2 Database Browser

The OneDB Database Browser now provides read-only access to authorized Db2 tables and views.

Administrators can:

  • Browse accessible Db2 schemas
  • View authorized tables and views
  • Inspect available columns
  • View records using pagination
  • Filter records using approved operators
  • View masked or tokenized values

All Database Browser requests are validated on the server to prevent access to unauthorized, inaccessible, or invalid database objects.

Pagination and Record Filtering

Db2 record pagination uses parameterized OFFSET and FETCH NEXT queries.

When primary-key metadata is available, OneDB uses the primary key to provide consistent record ordering across paginated requests.

Db2 record filtering uses metadata-validated column names, approved operators, and bound parameter values. This prevents arbitrary SQL expressions and unvalidated database identifiers from being submitted through the Database Browser.

Masking and Tokenization

Masking and tokenization policies configured through Field Settings are applied when Db2 values are displayed in the Database Browser.

Depending on the configured protection policy and user permissions, values may be displayed as plain text, masked data, or tokenized data.

Db2 Data-Type Handling

The Database Browser safely handles common Db2 data types, including:

  • Numeric values
  • Text values
  • Dates
  • Times
  • Timestamps
  • Boolean values
  • CLOB values
  • BLOB values
  • Binary values
  • NULL values

BLOB and binary values are represented using safe size markers instead of displaying raw binary content.

CLOB values follow the existing Database Browser maximum cell-display length.

Searchable Migration Connection Selectors

The Source Connection and Target Connection selectors in the Database Migration wizard are now searchable.

This enhancement makes it easier to locate database connections in environments with a large number of configured connections.

Db2 Migration is not included in this release.

Current Db2 Scope

Db2 support in OneDB v3.2.0 includes:

  • JDBC database connectivity
  • Authenticated connection validation
  • Schema, table, view, column, and primary-key discovery
  • Permission-aware metadata visibility
  • Field Settings configuration
  • Group permissions and Field Access configuration
  • Read-only Database Browser access
  • Record pagination and filtering
  • Masking and tokenization in the Database Browser
  • Safe handling of common Db2 data types
  • Server-side validation of database object access

Not Included in This Release

The following Db2 capabilities are not included in OneDB v3.2.0:

  • Db2 Listener support
  • DRDA protocol processing
  • Db2 client traffic interception
  • Protocol-level Query Audit capture
  • Protocol-level Query Whitelist enforcement
  • Wire-protocol result-set masking
  • Db2 Migration
  • Db2 frontend TLS support
  • Db2 backend TLS support
  • Db2 Database Browser export

Db2 support in this release uses direct JDBC connectivity between OneDB and the Db2 database. It does not yet provide Db2 Listener or client-traffic interception capabilities.

Known Limitations

  • Db2 tables and views without primary keys may not have deterministic record ordering across paginated requests.
  • Db2 CLOB values are limited by the existing Database Browser maximum cell-display length.
  • Db2 BLOB and binary values are represented using safe size markers and are not displayed as raw content.
  • Db2 metadata visibility requires additional read-access validation because the IBM JDBC driver may return metadata for objects that the connected user cannot query.
  • Db2 frontend and backend TLS support is not available in this release.