Release Date: May 2026
Release Type: Feature Release
Branch: 2.5.0
New Features
Secure Connection Support
OneDB v2.5.0 introduces Secure Connection support for database connections and proxy listeners.
This feature allows OneDB to support encrypted database traffic in supported deployment scenarios, helping improve the security of communication between client applications, OneDB listeners, and backend databases.
Secure Connection support is available for:
- PostgreSQL
- MySQL
- Microsoft SQL Server
- Oracle
Secure Database Connection
OneDB can now be configured to connect more securely to backend databases using TLS/SSL, depending on the selected database engine and customer environment.
This helps protect database traffic between OneDB and the backend database server.
Secure Proxy Listener Support
OneDB proxy listeners can now support secure client connections and forward database traffic based on the configured connection mode.
Supported connection patterns include:
| Connection Pattern | Description |
|---|---|
| Secure client to OneDB, plain OneDB to database | Client traffic is encrypted when connecting to the OneDB listener. |
| Secure client to OneDB, secure OneDB to database | Both client-to-OneDB and OneDB-to-database traffic use secure connections. |
| Plain client to OneDB, secure OneDB to database | Backend database traffic is secured between OneDB and the database server. |
Oracle Secure Connection Support
Oracle Secure Connection support has been added for both database connections and proxy listener traffic.
When Secure Connection is enabled for Oracle, OneDB can use secure Oracle TCPS connectivity using the configured service name.
Enhancements
Listener Reload Stability
Listener reload behavior has been improved, especially when switching between secure and non-secure listener modes.
This helps reduce potential reload issues such as port conflicts during listener restart operations.
Field Settings Reliability
Field Settings loading behavior has been improved when connection detail information is missing, invalid, or still pending.
OneDB also handles Field Settings more safely when database connections are deleted, helping prevent old or deleted connection policies from being reused accidentally.
Connection Cleanup Improvements
Connection deletion now performs safer cleanup for related configuration data.
This helps keep OneDB configuration more consistent after a database connection is removed.
Bug fixes
- Fixed Field Settings page loading issues caused by missing or invalid connection details.
- Improved fallback display when connection detail information is not available.
- Improved Field Settings lookup accuracy by validating the related connection.
- Improved cleanup of related Field Settings when a connection is deleted.
- Improved listener cleanup before restart.
- Ensured the clean build script is executable.
Security Updates
OneDB v2.5.0 improves secure database connectivity by adding Secure Connection support for supported database engines and proxy listener traffic.
This release helps strengthen encrypted communication options for database access through OneDB.
Known Notes
Secure listener mode is currently supported for PostgreSQL, MySQL, Microsoft SQL Server, and Oracle.
For Oracle secure connections, the current implementation uses service name based TCPS connectivity. Some advanced Oracle wallet or certificate trust configurations may still require manual setup depending on the customer environment.
For Microsoft SQL Server, Secure Connection should be enabled when encrypted traffic is required between OneDB and the backend database.
Customers should verify certificate, trust, and network configuration based on their own database environment before enabling Secure Connection in production.
Summary
OneDB v2.5.0 adds Secure Connection support across supported database engines and proxy listeners.
This release improves encrypted database connectivity, strengthens listener reload behavior, and includes reliability improvements for Field Settings and connection cleanup.