Network
The diagram provides a comprehensive overview of Axidian Access component interactions. You can adapt it based on your use cases and requirements.
Load balancers represent optional system elements, 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.
Interaction between main Axidian Access components in the network infrastructure is carried out through HTTP and HTTPS protocols.
| Name | Protocol | Incoming port | Outgoing port |
|---|---|---|---|
| Core Server | TCP/UDP | 80(http) 443(https) | 49152- 65535 |
| Management Console | TCP/UDP | 80(http) 443(https) | 49152- 65535 |
| Log Server (Windows Event) | TCP/UDP | 80(http) 443(https) | 49152- 65535 |
| Log Server (MS SQL) | TCP/UDP | 1433 | 49152- 65535 |
| Log Server (PostgreSQL) | TCP/UDP | 5432 | 49152- 65535 |
| Axidian Access MS SQL Database | TCP/UDP | 1433 | 49152- 65535 |
| Axidian Access PostgreSQL Database | TCP/UDP | 5432 | 49152- 65535 |
| Active Directory | DNS | 53 | 49152- 65535 |
| LDAP | 389 (LDAP) / 636 (LDAPS)3268 (LDAP) / 3269 (LDAPS) | 49152- 65535 | |
| Kerberos | 88 | 49152- 65535 | |
| Axidian Key Server | TCP/UDP | Configured on the AK server side | 49152- 65535 |
| Axidian Key Server MS SQL Database | TCP/UDP | 1433 | 49152- 65535 |
| User Console | TCP/UDP | 80(http) 443(https) | 49152- 65535 |
| ADFS Extension | TCP/UDP | 80(http) 443(https) | 49152- 65535 |
| IIS Extension | TCP/UDP | 80(http) 443(https) | 49152- 65535 |
| NPS RADIUS Extension | TCP/UDP | 80(http) 443(https) | 49152- 65535 |
| RDP Windows Logon | TCP | 3389 | 49152- 65535 |
| TCP/UDP | 80(http) 443(https) | 49152- 65535 | |
| Identity Provider | TCP/UDP | 80(http) 443(https) | 49152- 65535 |