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 used. The 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 a
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.
As example:
...
COS APP → COS RT → COS SC
...
Token Signing (Optional)
A certificate with which the private key can be exported is required for Token signing.