Skip to main content

Network

Interaction between main Axidian Access components in the network infrastructure is carried out through HTTP and HTTPS protocols.

Load balancers represent an optional system element, they are not built into Axidian Access and can be used in any quantity. The number of the Core Server, Axidian Key Server, Log Server components can also vary depending on client needs.

NameProtocolIncoming portOutgoing port
Core ServerTCP/UDP80(http) 443(https)49152- 65535
Management ConsoleTCP/UDP80(http) 443(https)49152- 65535
Log Server (Windows Event)TCP/UDP80(http) 443(https)49152- 65535
Log Server (MS SQL)TCP/UDP143349152- 65535
Log Server (PostgreSQL)TCP/UDP543249152- 65535
Axidian Access MS SQL DatabaseTCP/UDP143349152- 65535
Axidian Access PostgreSQL DatabaseTCP/UDP543249152- 65535
Active DirectoryDNS5349152- 65535
LDAP389 (LDAP) / 636 (LDAPS)3268 (LDAP) / 3269 (LDAPS)49152- 65535
Kerberos8849152- 65535
Axidian Key ServerTCP/UDPConfigured on the AK server side49152- 65535
Axidian Key Server MS SQL DatabaseTCP/UDP143349152- 65535
User ConsoleTCP/UDP80(http) 443(https)49152- 65535
ADFS ExtensionTCP/UDP80(http) 443(https)49152- 65535
IIS ExtensionTCP/UDP80(http) 443(https)49152- 65535
NPS RADIUS ExtensionTCP/UDP80(http) 443(https)49152- 65535
RDP Windows LogonTCP338949152- 65535
TCP/UDP80(http) 443(https)49152- 65535
Identity ProviderTCP/UDP80(http) 443(https)49152- 65535