This layout is recommended for pilot implementations to familiarize yourself with Axidian and perform demonstrations. All system components, required providers, and integration modules are installed on one computer. Integration modules can be deployed on different computers.
| Server name | Requirement | Axidian Access components |
|---|
| Core Server PC | Required component | Core Server, Log Server, Management Console |
| Core Server PC | Optional component | Identity Provider |
| Core Server PC | Required component. The type of authentication method depends on the final scenario. | Axidian Access providers |
| Core Server PC | Required component. The type of integration module depends on the final scenario. | Axidian Access integration modules |
| Axidian Access External PC | Optional component | Axidian Key Server, User Console |
| Server name | CPU | RAM | HDD | Network |
|---|
| Core Server PC | 4 cores | 8 GB | 200 GB | 100 Mbps |
| Axidian Access External PC | 4 cores | 8 GB | 100 GB | 100 Mbps |
This layout is recommended for production implementations. Critical system nodes are duplicated to ensure fault tolerance. The Axidian Access Management Console component is installed on one of the Axidian Access servers (Core Server). To configure load distribution between components, you must use a third-party load balancer.
| Server name | Requirement | Axidian Access components |
|---|
| Core Server\Log Server | Required component | Core Server, Log Server |
| Core Server\Management Console\Identity Provider | Required component. Identity Provider is required only for scenarios where authenticator enrollment for external users is needed. | Core Server, Management Console, Identity Provider |
| Axidian Key Server\User Console | Optional component. Axidian Key Server is required only for scenarios using push authentication. User Console is required for authenticator enrollment for external system users. | Axidian Key Server, User Console |
| Axidian Key Server\User Console | Optional component. Only for scenarios using push authentication. | Axidian Key Server, User Console |
| Axidian Access Extensions | Required component. The type of integration module depends on the final scenario. | Axidian Access integration modules |
| Load balancer | System requirements depend on the selected load balancer. | Load balancing is performed by third-party components. |
The table shows the recommended system requirements for deploying a production infrastructure for up to 10,000 users.
| Server name | CPU | RAM | HDD | Network |
|---|
| Core Server\Log Server | 8 cores | 8 GB | 200GB | 100 Mbps |
| Core Server\Management Console\Identity Provider | 8 cores | 8 GB | 200GB | 100 Mbps |
| Axidian Key Server\User Console | 8 cores | 8 GB | 150GB | 100 Mbps |
| Axidian Key Server\User Console | 8 cores | 8 GB | 150GB | 100 Mbps |
| Axidian Access Extensions | System requirements depend on the selected integration module | | | |
| PC with Axidian Access DB and Axidian Access events #1 | 8 cores | 8 GB | 500GB | 100 Mbps |
| PC with Axidian Access DB and Axidian Access events #2 | 8 cores | 8 GB | 500GB | 100 Mbps |