Connect2id server 20.3
Connect2id server 20.3 restores support for MariaDB. It also changes how the server handles database and cache store operations to reduce the impact of slow backends on other requests.
MariaDB support restored
The Connect2id server previously used the MySQL dialect for both MySQL and MariaDB. After the upgrade to jOOQ 3.21 in Connect2id server 20.0, the generated queries no longer worked with MariaDB. Release 20.3 restores support for MariaDB 10.6 and later when the MariaDB dialect is explicitly selected.
When upgrading a MariaDB deployment to 20.3, keep
infinispan.configurationFile pointing to your existing MySQL configuration
file and
explicitly select the MariaDB dialect. Set dataSource.sqlDialect to
MARIADB_10_6 in the selected XML configuration or pass the following Java
system property at startup:
-DdataSource.sqlDialect=MARIADB_10_6
The SQL dialect defaults to MySQL. See the
database configuration guide
for details on selecting the Infinispan configuration and setting
connection properties.
More responsive SQL, DynamoDB and Redis stores
Slow database calls and long-running tasks such as expired-record cleanup or bulk scans can tie up threads that Infinispan needs for other cache work. Connect2id server 20.3 changes how the stores handle that work:
- SQL and Redis now use Infinispan’s
BlockingManagerto keep blocking operations off its non-blocking threads. This covers store startup and shutdown, SQL operations including expired-record cleanup, and Redis reads, writes and bulk scans. - DynamoDB now uses an asynchronous client, including for paginated
reads and checks for resource readiness. Threads are free to do other
work while DynamoDB responds. Infinispan’s
BlockingManagerhandles the remaining blocking work in expired-record cleanup.
These changes help the server stay responsive under load by keeping threads available for other cache work when a backend is slow.
Other database and clustering fixes
The default Microsoft SQL Server JDBC URL now sets
sendStringParametersAsUnicode=false to avoid implicit character
conversions that can interfere with index use and contribute to deadlocks.
This release also fixes JGroups channel startup in replicated Infinispan
configurations backed by SQL or DynamoDB.
See the release notes for the full list of configuration changes and fixes.
Download 20.3
For the signature validation: Public GPG key
Standard Connect2id server edition
Apache Tomcat package with Connect2id server 20.3: Connect2id-server.zip
GPG signature: Connect2id-server.zip.asc
SHA-256: 130b71c318c0c8c7fd79052e4a9eb4844b397c373f2fb81af26dfd4fe70563a6
Connect2id server 20.3 WAR package: c2id.war
GPG signature: c2id.war.asc
SHA-256: 63156608af9e71a6e0257c0efbe6c3e314ab2ee933527b3d5852f4e9c4de51a5
Multi-tenant edition
Apache Tomcat package with Connect2id server 20.3: Connect2id-server-mt.zip
GPG signature: Connect2id-server-mt.zip.asc
SHA-256: 8c5b2b23ad33b4a55583d44060273c5a02ca78887291021ab3c1fd6a3993c169
Connect2id server 20.3 WAR package: c2id-mt.war
GPG signature: c2id-mt.war.asc
SHA-256: 847ef254ad2ced618291ec4e5c3350ab16f2ce90454216b3f98937123cb20bf9
Questions?
For technical questions about this new release contact Connect2id support. To purchase a production license for the Connect2id server, renew or upgrade your support and updates subscription, email our sales.
Release notes
20.3 (2026-11-19)
Summary
-
Restores support for MariaDB 10.6 and later, which was interrupted in release 20.0. When upgrading to 20.3, keep
infinispan.configurationFilepointing to your existing MySQL Infinispan configuration and explicitly select the MariaDB dialect by settingdataSource.sqlDialecttoMARIADB_10_6. -
The Connect2id server now runs all SQL store operations through Infinispan’s
BlockingManager, including startup, shutdown, and expired-record cleanup. This keeps slow database calls from tying up threads that handle other cache work, helping the server stay responsive under load and reducing the impact of database slowdowns on unrelated requests. -
The Connect2id server now uses asynchronous DynamoDB operations, including paginated reads and checks for resource readiness. This frees up threads while DynamoDB responds and keeps the remaining blocking work for expired-record cleanup off Infinispan’s non-blocking threads, helping the server stay responsive under load or during DynamoDB slowdowns.
-
The Connect2id server now uses Infinispan’s
BlockingManagerfor Redis store startup and shutdown, reads and writes, and bulk scans. This keeps waits for Redis off Infinispan’s non-blocking threads, helping the server stay responsive when Redis is slow or bulk operations are in progress.
Configuration
-
/WEB-INF/infinispan-*.xml
- Upgrades the XML schema to Infinispan 16.3
-
/WEB-INF/infinispan-*-mysql.xml
- Adds a
dataSource.sqlDialectproperty, which defaults toMySQL. For MariaDB 10.6+, set it toMARIADB_10_6in the selected Infinispan XML configuration or override it with the Java system propertydataSource.sqlDialectset toMARIADB_10_6.
- Adds a
-
/WEB-INF/infinispan-*-sqlserver.xml
- The default
dataSource.urlproperty includes the JDBC parametersendStringParametersAsUnicode=falseto improve performance and reduce locking issues in Microsoft SQL Server by preventing implicit character conversions that may lead to inefficient query execution plans. This adjustment allows the database to utilise indexes more effectively, and thus avoid locking errors (reported as SQL Server error1205).
- The default
Resolved issues
-
Restores compatibility with MariaDB 10.6 and later following the upgrade to jOOQ 3.21 in release 20.0. The SQL store now generates MariaDB-compatible SQL when
dataSource.sqlDialectis set toMARIADB_10_6(issue server / 1249). -
Fixes the authorisation store schema for MySQL and MariaDB so the
tspcolumn inexpended_tokensdefaults toNULL. With the database’sexplicit_defaults_for_timestampsetting disabled, legacyTIMESTAMPrules could give the column an implicit non-NULLdefault. The schema now declares the column nullable with an explicitNULLdefault, so its behaviour is independent of that setting (issue authz-store / 264). -
Fixes deferred SQL store startup with shared JDBC connection pools so the SQL store is reported as started only after the referenced pool and SQL context are ready (issue sql-store / 45).
-
Prevents SQL store paged expired-entry reaping from looping indefinitely when a full page contains malformed records (issue sql-store / 46).
-
SQL store JDBC operations are made to run through Infinispan’s
BlockingManager, including startup, shutdown, and expiration-reaper work (issue sql-store / 47). -
Restores
IS0141logging of illegal SQL records during expiration purge (issue sql-store / 48). -
The default Microsoft SQL Server JDBC connection URL now includes the
sendStringParametersAsUnicode=falseproperty to prevent implicit character conversions and thus avoid locking errors (reported as SQL Server error1205) (issue server / 1253). -
Migrates DynamoDB operations to the asynchronous client and HTTP transport, using async paginators and waiters, with Infinispan’s
BlockingManagerhandling the remaining blocking expiration purge operations (issue dynamodb / 40). -
Fixes DynamoDB XML configuration parsing to make
query-executorandindex-attributesindependent of attribute order (issue dynamodb / 37). -
Fixes DynamoDB expired-entry purging to enforce the configured purge limit within each scan page, preventing the limit from being exceeded by up to an entire page (iss issue dynamodb / 38).
-
Redis lifecycle, CRUD and bulk iteration operations are made through Infinispan’s
BlockingManager(issue redis-store / 24). -
Continues Redis SCAN iteration across empty non-terminal result pages, preventing iteration from stopping before the final cursor (issue redis-store / 23).
-
Makes DynamoDB JGroups
store_debug_infoconfigurable via ajgroups.dynamodb_ping.store_debug_infoJava system property and assigns it a default valuefalse(issue server / 1257). -
Fixes JGroups channel startup for Infinispan replication configurations with an SQL store, affecting prior Connect2id server 20.x releases (issue server / 1259).
-
Fixes JGroups channel startup for Infinispan replication configurations with DynamoDB, affecting prior Connect2id server 20.x releases (issue server / 1260).
Dependency changes
-
Updates to com.nimbusds:oauth2-oidc-sdk:11.39
-
Updates to com.nimbusds:tenant-registry:10.1
-
Updates to com.nimbusds:c2id-key-store:2.4
-
Updates to com.nimbusds:oidc-session-store:23.3
-
Updates to com.nimbusds:oauth2-authz-store:30.2
-
Updates to com.nimbusds:software-statement-verifier:2.4
-
Upgrades to Infinispan 16.3.2
-
Updates to com.nimbusds:infinispan-cachestore-common:5.0.2
-
Upgrades to com.nimbusds:infinispan-cachestore-sql:9.2.2
-
Updates to org.jooq.pro:jooq:3.21.9
-
Updates to org.mariadb.jdbc:mariadb-java-client:3.5.11
-
Updates to com.nimbusds:infinispan-cachestore-dynamodb:9.0.1
-
Updates to com.nimbusds:jgroups-dynamodb-ping:2.0.1
-
Updates to AWS SDK 2.57.11
-
Updates to com.nimbusds:infinispan-cachestore-redis:12.2
-
Updates to net.minidev:json-smart:2.6.1
-
Updates to io.micrometer:micrometer-core:1.17.1
-
Updates to commons-codec:commons-codec:1.23.0
-
Updates to BouncyCastle 1.87
-
Updates to Dropwizard Metrics 4.2.40