App Suite Middleware
General
SCR-1482
Summary: Added redis.tls chart value
Whether to use TLS to connect to the Redis endpoint can now be configured using redis.tls.enabled
and redis.cache.tls.enabled
.
SCR-1480
Summary: Updated lettuce library from v6.5.0 to v6.5.1
Updated lettuce library from v6.5.0 to v6.5.1 in bundle io.lettuce
- lettuce-core-6.5.1.RELEASE.jar
3rd Party Libraries/License Change
SCR-1481
Summary: Updated Fabric8 libraries from v6.10.0 to v6.13.4
Updated Fabric8 libraries from v6.10.0 to v6.13.4 in "io.fabric8.kubernetes" bundle
- kubernetes-client-6.13.4.jar
- kubernetes-client-api-6.13.4.jar
- kubernetes-httpclient-jdk-6.13.4.jar
- kubernetes-model-admissionregistration-6.13.4.jar
- kubernetes-model-apiextensions-6.13.4.jar
- kubernetes-model-apps-6.13.4.jar
- kubernetes-model-autoscaling-6.13.4.jar
- kubernetes-model-batch-6.13.4.jar
- kubernetes-model-certificates-6.13.4.jar
- kubernetes-model-common-6.13.4.jar
- kubernetes-model-coordination-6.13.4.jar
- kubernetes-model-core-6.13.4.jar
- kubernetes-model-discovery-6.13.4.jar
- kubernetes-model-events-6.13.4.jar
- kubernetes-model-extensions-6.13.4jar
- kubernetes-model-flowcontrol-6.13.4.jar
- kubernetes-model-gatewayapi-6.13.4.jar
- kubernetes-model-metrics-6.13.4.jar
- kubernetes-model-networking-6.13.4.jar
- kubernetes-model-node-6.13.4.jar
- kubernetes-model-policy-6.13.4.jar
- kubernetes-model-rbac-6.13.4.jar
- kubernetes-model-resource-6.13.4.jar
- kubernetes-model-scheduling-6.13.4.jar
- kubernetes-model-storageclass-6.13.4.jar
SCR-1479
Summary: Updated Netty libraries from v4.1.114 to v4.1.115
Updated Netty libraries from v4.1.114 to v4.1.115 in bundle io.netty
- netty-buffer-4.1.115.Final.jar
- netty-codec-4.1.115.Final.jar
- netty-codec-dns-4.1.115.Final.jar
- netty-codec-http2-4.1.115.Final.jar
- netty-codec-http-4.1.115.Final.jar
- netty-codec-socks-4.1.115.Final.jar
- netty-common-4.1.115.Final.jar
- netty-handler-4.1.115.Final.jar
- netty-handler-proxy-4.1.115.Final.jar
- netty-resolver-4.1.115.Final.jar
- netty-resolver-dns-4.1.115.Final.jar
- netty-transport-4.1.115.Final.jar
- netty-transport-native-unix-common-4.1.115.Final.jar
Configuration
SCR-1485
Summary: New options for Redis Connector
Added new lean options for the Redis connector
com.openexchange.redis.connection.pool.newConnectionIfWaitExceeded
Specifies whether to establish a new connection if waiting for an available connection in pool is exceeded. Default value is"true"
. Neither reloadable, nor config-cascade awarecom.openexchange.redis.cluster.periodicTopologyRefreshMillis
Defines the interval in milliseconds for periodic refreshing of the the cluster topology. Only effective if connecting against a Redis Cluster; e.g."com.openexchange.redis.mode"
is set to"cluster"
. Default value is"600000"
. Neither reloadable, nor config-cascade aware
SCR-1477
Summary: New property to select default collection for new contacts via iOS / CardDAV
In the Contacts App on iOS, it is not possible to pick a certain folder while creating a new contact within the CardDAV account. Instead, the iOS client creates new contacts in a somehow randomly chosen folder of the account, which could also be the "Global Address Book" or the "Collected Contacts" folder, or even folders that are shared from others. Therefore, as the user cannot influence the target folder, an implicit workaround is in place so that new contacts are always created within the user's default contacts folder on App Suite. Within the iOS client, this is reflected after the next synchronization cycle as well.
To influence the applied fallback logic, the following lean configuration property is introduced:
com.openexchange.carddav.iosFallbackToDefaultCollectionForNewResources
Possibly settings are:
{}always{
}: New contacts are always created within the user's default contacts folder on App Suite{}disabled{
}: Contacts are created within the folder targeted by the client, but rejected on insufficient permissions{}insufficientPermissions{
}: Contacts are created within the folder targeted by the client, falling back to the user's default folder on insufficient permissions
It defaults to always
so that contacts are created in the user's default contacts folder independently of which folder is targeted by the client.
The new property is reloadable and config-cascade-aware.