Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Version 2022 Spring is not yet released ...

The following information as well as the linked information is intended to outline some of our current product developments for our yuuvis® Momentum 2022 Spring.

Like everything else in life, the best plans can change over time. The following article describes the current state of work, but it is important to understand that the details are for information purposes only and are not to be understood as binding commitments.

OPTIMAL SYSTEMS reserves the right to make changes in the planning, development and release of products and their features and functions at its sole discretion.

When updating your yuuvis® Momentum installation to version 2022 Spring, manual configuration changes are required for some services. 

Table of Contents

Breaking Changes

The following Breaking Changes are incompatible changes we had to deploy into operation, and therefore you—as a yuuvis® user—need to be aware of them and take action accordingly.


Client Services & Client Development

Developer Libraries

Object Creation Permissions

The permission to create new objects is now enabled via a create permission within one of the roles defined via a role set. The YUUVIS_CREATE_OBJECT role does no longer allow object creation. You need to adjust your corresponding role set accordingly.

Action: Update your roles as described here. Use the following condition:

<condition>system:objectTypeId = 'appClient:minidoc' AND system.secondaryjectTypeIds = 'appClient:minidoc'</condition>

Configurations Enabling new Features

Some new features require manual configuration in order to operate properly after the update to the new yuuvis® Momentum version.

Core

Fail-safe AUTHENTICATION Service

In order to enable the shared usage of the session state for multiple instances of the AUTHENTICATION service, the session state has to be stored in a Redis database. In the default configuration of yuuvis® Momentum, the session state is stored by the individual AUTHENTICATION service instances. Thus, in order to enable the central storage of the session state in Redis, manual configuration steps are required.

  • Extend the authentication-prod.yml configuration file by the following lines:

    spring.session.store-type: redis
management.health.redis.enabled: true


  • Add the redis profile to the AUTHENTICATION service:

    • Run the command:

      kubectl -n yuuvis edit deploy authentication


    • Extend the SPRING_PROFILES_ACTIVE environment variable with redis.
  • Restart all instances of the AUTHENTICATION service.

    • For example, instance 2 can be restarted using the following command:

      kubectl -n yuuvis scale deploy authentication --replicas=2



  • No labels