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 certificte 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.
For each connection between the CoreOne Application Services and the CoreOne System Connectors / CoreOne Secure Router, a seperate separate certificate is required per server, which supports “Server Authentication” and “ Client “Client Authentication”. In addition, the corresponding public certificate must be available on the other side.
Als Beispiel
As example:
URL | Service | Certificate | Subject Alternativ Name |
|---|---|---|---|
https://demo.itsense.ch | CoreOne Suite Web Services | CoreOne Suite Web Services | demo.itsense.ch oder *itsense.ch |
https://openid.itsense.ch | CoreOne Suite AuthAuthentication Services | CoreOne Suite AuthAuthentication Services | openid.itsense.ch oder *itsense.ch |
https://api.itsense.ch | CoreOne Suite API | CoreOne Suite API | api.itsense.ch oder *itsense.ch |
https://portal.itsense.ch | CoreOne Suite Self Service Portal | CoreOne Suite Self Service Portal | portal.itsense.ch oder *itsense.ch |
COS WEB < - > COS APP | Internes Zerifikatinternal certificate | IAM.Genreal |
...
COS WEB < - >Endgerät (SSL certificate for UI)
COS Token Signing (For signing the Tokens)
COS AUTH < - > Endgerät (SSL certificate for OpenID)
COS WEB < - > COS APP (Internal communication)
COS APP < - > COS RT (Internal communication)
COS RT < - > COS SC / COS RT (Internal communication)
...