Connect2id server 7.8.3

Posted 2019-02-21

This update of the Connect2id server is intended for deployments that use a custom Redis setup to store short-lived and cached data:

  • A Redis proxy that doesn't support the SELECT operation (multiple databases), such as twemproxy.

  • To allow data to be stored in the default Redis database (in index zero). Prior to 7.8.3 the Connect2id server would not allow use of the default Redis database, to avoid potential object deserialisation errors when using AWS ElastiCache (AWS puts a special meta key in the default database which can cause object deserialisation errors).

See the release notes below for more information.

Download

To download a ZIP package of Connect2id server 7.8.3:

https://connect2id.com/assets/products/server/download/7.8.3/Connect2id-server.zip

SHA-256: fdc56573dbd8843154555e3cf9172a6a64e7092b0f9fd7b92727208e7f1395a0

As WAR package only:

https://connect2id.com/assets/products/server/download/7.8.3/c2id.war

SHA-256: a90e665dfe30ffddea03b9da47b3c32bb6e2f90440866c4f69b1a45da20659ca

Questions?

Contact Connect2id support.


Release notes

7.8.3 (2019-02-21)

Resolved issues

  • Updates the Redis configuration check to log an OP0116 warning when detecting an Infinispan cache / map that is assigned the default Redis database (zero). The default database must not be used in AWS ElastiCache to prevent object serialisation errors due to the ElastiCacheMasterReplicationTimestamp meta key created by the AWS ElastiCache clustering service. Previously this condition resulted in aborting Connect2id server startup. The Redis configuration check which detects database number clashes for the same Redis host will continue to prevent Connect2id server startup (issue server/414).

Dependency changes

  • Updates to com.nimbusds:common:2.28.1