4.0.2 Deprecations and breaking changes

Ignite cluster manager

Already ignored attribute defaultLockTimeout in the cacheConfiguration was removed

• https://github.com/vert-x3/vertx-ignite/pull/100

All toConfig methods were moved from the Options objects to the ConfigHelper class

• https://github.com/vert-x3/vertx-ignite/pull/106

Deprecation of some IgniteSslOptions properties

• https://github.com/vert-x3/vertx-ignite/pull/106

The options keyAlgorithm, keyStoreType, keyStoreFilePath, keyStorePassword, trustStoreFilePath and trustStorePassword are now deprecated and will be removed in version 4.1
For configuring JKS stores use the well known Vert.x JksOptions jksKeyCertOptions and jksTrustOptions

Auth

PubSecKeyOptions.getBuffer() returns Buffer instead of String

• https://github.com/vert-x3/vertx-auth/pull/449

This was a leftover from the 4.0.0 release. It was assumed (wrongly) that secrets could be safely be stored in a String variable. Has it has been shown by the community the safest approach and compatible way to handle them is to store them as Buffers. Only the getter API is changing as it is only used by the vert.x API. The setter API remains as String and an overload for Buffer is added to handle without breaking changes to the existing user code.

Oauth2Options

• Deprecated properties: useBasicAuthorizationHeader and clientSecretParameterName have been removed as they were not used internally already.