Youforce Portal 2020-06-06 EN

[#1]

Announcement

Transition to technical protocol TLS 1.2 for IBU.

Why

Visma | Raet stopped supporting TLS 1.0 and TLS 1.1 for all products except for the interfaces (IBU) last 30 November 2019.  Through this adaptation Visma | Raet takes a step towards an even safer and more reliable Youforce as of 6 June of 2020. As of that date, Visma | Raet will stop supporting TLS 1.0 and TLS 1.1 for IBU as well.

Transport Layer Security (TLS) is the technical protocol that takes care of an important function in the browser: encryption of data traffic between your computer and our servers. Currently, there are three prevalent TLS protocols: 1.0, 1.1 and 1.2. For now, IBU supports all three versions. The use of TLS 1.2 entails the application of the latest and safest encryption techniques.
Visma | Raet will disable the older and less safe protocols (TLS 1.0 and TLS 1.1) for IBU.

How

Some old browsers do not support TLS 1.2. These can no longer be used to connect to Youforce as they do not use the corresponding TLS 1.2 protocol. You will have to use a newer browser.
Links to and interfaces with Youforce that connect using TLS 1.0 or TLS 1.1 will also no longer function after the transition to TLS 1.2.

IBU Server will not be available during the maintenance interval on 6 June, from 09:00 to 17:00 (CET). File exchange in Send & Receive and the IBU client executable in standalone mode cannot be used during the maintenance interval either. If you have planned critical file exchanges during this period, we advise you to reschedule these activities. Please contact your administrator.

Your action

Ensure that the links that are managed by yourself support TLS 1.2 prior to the specified date. As of 6 June of  2020, all Visma | Raet IBU interfaces will only support TLS 1.2.

Impact for IBU Standalone

If your organization uses a scheduler to automatically upload files to or download files from the Youforce server using IBU client in standalone mode, you should pay special attention to the following.

• File exchange with IBU standalone will not work during the maintenance interval.
• IBU standalone will start processing files left on the client or server after the maintenance has ended, on the first automatically scheduled start afterward.
• If IBU standalone tries to connect to IBU server during the maintenance interval, error messages will be generated and logged. Depending on your local configuration, e-mails may also be sent to your organization's administrator. Such error messages are normal and can be ignored.
• If IBU server goes down in the middle of processing a file exchange, the transfer may fail. In this case, an appropriate error message will also be logged. In some cases, it might be necessary to send or receive the corresponding file manually afterward. If the requested file has disappeared from the server list, you may contact the Raet Service Desk to have it restored.
• If your organization would rather prevent the above-mentioned errors, you are advised to switch off your local scheduler for IBU standalone during the maintenance interval. Your IT professional can take care of this, or you may contact your Raet consultant.

Publishing Date : 6/4/2020