Introduction
Depending on the deployment of the CoreOne Suite, there might be a need to open up specific connections and ports in Firewalls and / or Web Application Firewalls. The subsequent table and diagram document all the connections within the CoreOne Suite. For more information on the required certificates see System requirement Certificates.
ID | Point A | Point B | Direction | Protocol | Default Port | Encryption | Definition | Path for certificates |
|---|---|---|---|---|---|---|---|---|
A | CoreOne Web Services | CoreOne Authentication Services | Both Ways (A <--> B) | HTTPS / OIDC | 443 | Yes | Authentication | Web application configuration |
B C D E | CoreOne Web Services | CoreOne Application Services | Both Ways (A <--> B) | WCF WCF HTTPS HTTPS | 8008 8005 7000 8000 | Yes Yes Yes Yes | Application Communication HTTPS Fallback TCP Health Check API | Web application configuration |
F Q | CoreOne Authentication Services | CoreOne Application Services | One Way (A → B) One Way (A → B) Both Ways (A <--> B) | HTTPS HTTP HTTPS / OIDC | 8000 7000 443 | Yes No Yes | API Health Check Authentication | IIS-Manager |
G | CoreOne Authentication Services | CoreOne Database Services | One Way (A → B) | TCP | 3306 | Yes | Database Connection | |
R | CoreOne Authentication Service | Third Party Clients | Both Ways (A <--> B) | OIDC | 443 | Yes | OIDC Clients | |
H | CoreOne Application Services | CoreOne Database Services | One Way (A → B) | TCP | 3306 | Yes | Database Connection | Backend application wrapper |
M | CoreOne Application Services | CoreOne Router / CoreOne System Connector | One Way (A → B) | TCP | 9000 | Yes | Port Configurable | Backend application configuration |
J | CoreOne Self-Service Portal | CoreOne Application Services | One Way (A → B) | HTTPS | 8000 | Yes | API | |
I L | CoreOne Self-Service Portal | CoreOne Authentication Services | One Way (A → B) Both Ways (A <--> B) | HTTPS HTTPS / OIDC | 8000 443 | Yes Yes | API Authentication | |
K | CoreOne Router | CoreOne System Connector | One Way (A → B) | TCP | 9000 | Yes | Port Configurable | |
N | Third-party Systems | CoreOne API | One Way (A → B) | TCP | 8000 | Yes | ||
O | CoreOne Database Service | Reporting Tools | Both Ways (A <--> B) | TCP | 3306 | Yes | ||
S | CoreOne Application Services / Universal Connector | Source Systems (e.g. SAP, Navision) | Both Ways (A <--> B) | Multiple | Multiple | Yes | Global setting value | |
P | CoreOne System Connector | Target Systems (eg. Active Directory, Exchange ) | Both Ways (A <--> B) | Multiple | Multiple | Yes | Appcustomer target network | |
T | CoreOne Workflow Runner | CoreOne Application Service | Both Ways (A <--> B) | TCP | 6000 | Yes | API | |
U | CoreOne Workflow Runner | CoreOne Workflow Dashboard | Both Ways (A <--> B) | TCP | 9001 | Yes | API | |
W | CoreOne Workflow Runner | Redis | Both Ways (A <--> B) | TCP | All Communication Ports from Redis Master and Slave Nodes. See your Redis Node redis.conf file for these Ports. Default Communication Port is 6379.
The redis cluster users the following internal Ports (Y): | Yes | ||
V | CoreOne Workflow Runner | RabbitMQ | Both Ways (A <--> B) | TCP | 4369 The RabbitMQ Cluster users the following internal Ports (Z) | Yes | ||
X | CoreOne Workflow Runner | CoreOne Database Services | One Way (A → B) | TCP | 3306 | Yes | Database Connection | |
α | CoreOne Workflow Dashboard | CoreOne Authentication Services | Both Ways (A <--> B) | TCP | 443 | Yes |
