Skip to main content
Skip table of contents

S 39

Please note: Since release 39.5.25 (at least DB 25.0.0, at least S 39.0.0), PLANTA provides all of its software components (exception: Desktop Client) as a container solution. An OCI-compatible container runtime or platform, e.g. Docker, is required for the installation / operation of versions from 39.0.0 or for any update to these versions. For further information, see Installation of PLANTA project.

S 39.1.0 (manager, worker)

Features

Key

Description

711

Attributes can now also be read as binary data and stored in Base64-encoded form.
To do so, the relevant attribute must be added to the plantaUserData list in the ldap section of the PLANTA server's manager configuration and stored as the value “base64”.
In addition, the attribute must be added to the java.naming.ldap.attributes.binary entry. This entry can contain a list separated by blank spaces.

1128

Performance has been improved by increasing the default setting of the planta__server__database__max_parameters_in_statement parameter to “500”.
This prevents parameters from being moved to a temporary table for small queries.

1158

The JDBC driver has been updated to the latest version: mssql-jdbc-13.2.1.jre11
In this version, pre-encryption is activated by default.

1194

In the current Microsoft JDBC driver, encryption is activated by default. New parameters are now available for targeted control of encryption:
planta__server__hibernate__connection__encrypt = true
planta__server__hibernate__connection__trustServerCertificate = true
planta__server__hibernate__connection__trustStore = ""
planta__server__hibernate__connection__trustStorePassword = ""

1064

It is now possible to define parameters that are new and “unknown” to the server.
All parameters that begin with planta__server__ and have not yet been defined are assigned to a new parameter group called “unrelated,” which can be accessed in worker and customizing.
The parameter can be queried using its full name.

704

Parameters in SQL statements are now handed over in temporary tables. This also circumvents the limitation on the maximum number of parameters in both MSSQL and Oracle.

875

Hibernate Lib updated to version 5.6.15 and Hibernate Validator Lib updated to 6.2.5

1130

The default value of the planta__server__webservices__apikey_auth_filter_generic environment variable has been rectified and set from “true” to “false”.

1197

The new planta__server__database__typename server parameter allows you to set a database type.
Possible values: “mssql”, “oracle”, “postgres”
Using this parameters, the corresponding parameters are automatically set correctly.:

  • planta__server__database__type

  • planta__server__hibernate__dialect

  • planta__server__hibernate__connection__driver_class

The planta__server__database__type parameter should no longer be used and is set to “Deprecated”. Only planta__server__database__typename should be used from now on.

1197

The endpoint of the Prometheus interface can be changed using the planta__server__webservices__prometheus__entrypoint parameter.

The prefix of the metrics is now planta_server and no longer prometheus. This facilitates the assignment.

680

Prometheus Lib updated to version V1.3.10

  • Changed metrics name:
    Previous: planta_server_native_memory_pool_allocated_bytes_total
    New: planta_server_native_memory_pool_allocated_bytes

  • Changed labels:
    Previous format: labels always have a final comma, e.g.
    planta_server_track_active_sessions_by_mode{threadType="scheduler",} 0.0
    New format: labels without final comma, e.g.
    planta_server_track_active_sessions_by_mode{threadType="scheduler"} 0.0

684

The handling of custom deprecation messages has been improved.

1019

ExitCode 253 has been added. It shows that after data import the constraints could not be reactivated.

38

The Web Client can now also authenticate via OIDC JWToken. To do so, the Web Client sends the user and the AccessToken to the server. The server validates the token and uses the data it contains for login.

For this purpose, new environment variables have been implemented:

  • planta__server__secure__oidc__clientSecret

  • planta__server__secure__oidc__tenantId

  • planta__server__secure__oidc__jwksEndpoint_suffix

  • planta__server__secure__oidc__authority_prefix

  • planta__server__secure__oidc__idTokenEndpoint_suffix

  • planta__server__secure__oidc__scope

  • planta__server__secure__oidc__access_token_scope

  • planta__server__secure__oidc__issuer_prefix_1

  • planta__server__secure__oidc__issuer_prefix_2

  • planta__server__secure__oidc__issuer_prefix_3

  • planta__server__secure__oidc__jwksEndpoint_suffix_alternate

The URL of the idToken endpoint is composed as follows:
authority_prefix + tenantId + idTokenEndpoint_suffix

The URL of the jwks endpoint is composed as follows:
authority_prefix + tenantId + idTokenEndpoint_suffix

1147

DDL-SQL expressions with parameters are now treated separately.

S 39.0.4 (manager) and S 39.0.3 (worker)

Features

Key

Description

1024

The new planta__server__database__use_underscore_as_wildcard configuration parameter has been implemented to enable the option of disabling the default use of the underscore _ as a wildcard in search queries. In such a case, the _ character is interpreted as a normal character. This ensures that search queries are executed accurately, thereby improving performance. This option is particularly suitable for customers who, e.g., use underscores in object IDs.

To use this option, both server components, i.e., the manager and the worker, must be updated.

S 39.0.2 (Worker)

Bug Fixes

Key

Description

910

The removal of virtual Dis from SQL statements has been improved.

S 39.0.3 (manager)

Bug Fixes

Key

Description

930

Eliminates a security gap by updating libraries used for LDAP

S 39.0.2 (manager)

Bug Fixes

Key

Description

880

The Worker now starts correctly, even if the planta__server__gui__host variable does not have the entry 0.0.0.0 but the service host name.

890

For the MSSQL database, character encoding is enabled and set to utf-8 format.
For this purpose, new parameters have been implemented which are set automatically for the MSSQL database:

  • planta__server__hibernate__connection__useUnicode = true

  • planta__server__hibernate__connection__characterEncoding = utf-8

  • planta__server__hibernate__connection__CharSet = utf-8

S 39.0.1 (manager, worker)

Bug Fixes

Key

Description

661

Hibernate has been updated to version 5.6.5

672

Security gaps have been closed.

S 39.0.0 (manager, worker)

Features

Key

Description

323

Internal server communication has been improved: The protobuf messages can optionally be output in the log and thus enable better traceability.

171

The metrics of the Prometheus interface now consistently start with “planta_server” for uniform naming.

37

The server now uses the current CPython version 3.12.9 for improved stability and security.

332

Authentication now supports login via JWT token.

110

Saving of version information has been standardized. Version information is generated in JSON format with the following attributes:

  • server version (major/minor/patch) - date - commit hash.

A separate node is generated for each component: (manager / worker / client)
They can be retrieved from the customizing via the ppms.version_information function.

532

Exit codes from Linux/Signals have been complemented by comprehensible descriptions which are displayed upon abortion.

440

Logging at the start of a client session has been tidied up and unnecessary messages removed.

293

The Python function set_user_clipboard(content, mime_type) can be used to conveniently copy objects to the clipboard.

272

The "round" effect type has been included in the list of available effects.

365

The execution of migrations has been accelerated by excluding irrelevant packages.

255

Parameters for clientless sessions can now contain nested dictionaries, offering greater flexibility.

680

The monitoring interface has been set to depricated. Instead, the Prometheus interface or the Health end point should be used from now on.

Bug Fixes

Key

Description

29

The error that in the course of a day the utilization diagrams showed incorrect values after different scheduling runs has been eliminated. Previously this could only be resolved by replanning.

281

During LDAP import, the UUIDs are now retained consistently and ensure unique identification.

76

The user ID is reliably transmitted when using the server adapter without LDAP or OIDC to ensure correct authentication.

601

The Deviations module now processes data in a stable manner and without Python exception.

300

The creation of statements with virtual data items and relations to parent areas now works as intended.

90

The parsing of statements has been optimized so that literals are only replaced in the correct places.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.