Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Connect Server General

HTTPS, SSL, TLS: I want a secure connection between Connect Server and client (browser). What do I have to do?

Connect supports SSL and TLS. HTTPS must be activated so that data can be transmitted securely between Connect Server and client. A certificate is required for this. The certificate can be requested from third-party providers, or you can create it yourself. When the certificate is ready, it can be configured as described here.

How do I create a server certificate to use HTTPS?

The procedure for this depends heavily on the infrastructure used. In general, the procedure is as follows:

  1. Generate the private key for the server

  2. Creation of a certificate request for the server

  3. Signing of the certificate request by a trusted certification authority

  4. Creation of the .pfx file

An example of this flow using OpenSSL:

...

During execution, you will be asked to set the password for the private key. The cert.pfx file is then created. You can use this file and its password to configure the Connect Server for HTTPS. For more information, see the chapter Konfiguration Configuration (Connect 20212022).

Connect Server on Linux

Which Linux distributions are supported?

In principle, the The Connect Server should work under on all common Linux distributions. Our internal tests are currently carried out under the latest version of Suse (SLES), RedHat (CentOS), Ubuntu and Debian (only in combination with Docker).

...

Which Windows versions are supported?

The Connect Server can be operated run on Windows client versions from Windows 7 onwards as well as on Windows servers from Windows Server 2016 onwards.

...

In general, the operation of the Connect Server should be possible on all operating systems for which .NET 6 is available. This also applies to macOS. However, we are currently only testing on Windows and various Linux distributions.

Use of MS SQL database

Which collation should be used?

In our Galileo-internal systems we use "Latin1_General_CI_AS".

In general, however, all collations should work, as the communication with the database runs exclusively via Unicode and the sorting is always done by the C# coding of Connect.

However, if you can decide, use: "Latin1_General_CI_AS".

Problems and solutions

A list of known problems and their solutions can be found at the following link:

Connect -

...

Troubleshooting Guide