Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 44 Next »

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.

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

Failback 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

TCP

6000

9100

Yes

Yes

API

API

W

CoreOne Workflow Runner

Redis

Both Ways (A <--> B)

TCP

6379
16384
16379

The redis cluster users the following internal Ports (Y)
7001,7002,7003,7004,7005,7006,17001,17002,17003,17004,17005,17006

Yes

V

CoreOne Workflow Runner

RabbitMQ

Both Ways (A <--> B)

TCP

4369
5672
15672

The RabbitMQ Cluster users the following internal Ports (Z)
25672

Yes

X

CoreOne Workflow Runner

CoreOne Database Services

One Way (A → B)

TCP

3306

Yes

Database Connection

How-to article


Related article


  • No labels