Introduction

For secure communication between the CoreOne Web Services and the end devices, an SSL certificate is required that corresponds to the CoreOne Web Services. In other words, the subject alternative name of the certificate must match the URL of the Web. If the CoreOne Web Services and the CoreOne Applications Services are installed on the same system, the same certificate can be usedThe CoreOne Suite consists of multiple distributed services. To communicate between the services and to the end-user and to sign various things like tokens, certificates are used. So whenever you are planning on distributing a new service or a new installation, you will need to have some certificates ready. This page gives you an overview on the requirements.

For each connection between the CoreOne Application Services and the CoreOne System Connectors / CoreOne Secure Router, a separate certificate is required per server, which supports “Server Authentication” and “Client Authentication”. In addition, the corresponding public certificate must be available on the other side.

A full overview of all communication channels, ports and more check the page Connectivity (Network ports, protocols and certificates)

...

https://lucid.app/lucidchart/00160333-04a9-4d01-b436-7100d5f1fd6f/view?page=0_0&invitationId=inv_97d54472-2c7d-48b0-8ab6-00aa34c50b2c#

Here is an example of generally needed certificates

...

...

COS WEB < - >Endgerät (SSL certificate for UI)

...

COS Token Signing (For signing the Tokens)

...

COS APP < - > COS RT (Internal communication)

...

COS RT < - > COS SC / COS RT (Internal communication)

COS APP → COS RT → COS SC

...

Token Signing (Optional) 

A certificate with which the private key can be exported is required for Token signing.