Important
For the production environment, a separate X-Road Security Server must be deployed on separate infrastructure (physical or virtual), with its own IP address and DNS name, different from those of the test environment.
Please do not use the test environment's Security Server, or its IP address or DNS name, for production. The Security Servers of the test and production environments, and their corresponding network identifiers, must be kept separate.
Alongside the transition to the production environment, the test infrastructure must be maintained and continue to operate for testing purposes.
Joining ADEL¶
High-level steps to onboard your organization onto the Armenian Data Exchange Layer (ADEL) X-Road network.
Production onboarding will additionally involve membership agreements, SLAs, formal compliance review, production certificates.
1. Request access¶
Contact ADEL to register your organization on the ADEL network and to receive the artifacts required for configuration:
- Email: adel@isaa.am
When contacting ADEL, include your organization's official English name (as registered in the Legal Entities Registry; official abbreviations are allowed if it exceeds 50 characters), your member class, and your legal entity identification code (ՁԿԴ).
ADEL will provide:
- Configuration anchor
- Member code assigned to your organization
- Any access credentials needed
2. Prepare infrastructure¶
Provision a host for your Security Server. For the test instance, a single Security Server is sufficient — high-availability clustering is not required.
Minimum specifications
| Resource | Minimum |
|---|---|
| CPU | 2 cores (x86-64) |
| RAM | 4 GB |
| Disk | 100 GB |
| Network | 100 Mbps |
| OS | Ubuntu 24.04 LTS or Red Hat 9 |
Required network ports
| Port | Protocol | Scope | Purpose |
|---|---|---|---|
| 5500 | HTTPS | Public (inbound/outbound) | Data exchange between Security Servers |
| 5577 | OCSP | Public (inbound/outbound) | OCSP responses |
| 8080 | HTTP | Internal only | Internal service access |
| 8443 | HTTPS | Internal only | Internal service access |
| 4000 | HTTPS | Internal only | Administration UI |
3. Deploy the Security Server¶
Install the X-Road Security Server using one of the supported deployment methods (Ansible playbook for VMs, or Helm chart for Kubernetes).
See: Security Server Deployment Guide
4. Configure and register on the network¶
Using the configuration anchor and member code provided by ADEL:
- Upload the anchor and perform initial configuration
- Activate soft tokens and add the timestamping service
- Generate CSRs for authentication and signing certificates
- Upload the issued certificates and register the authentication certificate
- Create your first subsystem and submit the registration request to the Central Server
See: Security Server Configuration Guide
5. Publish or consume services¶
Once your Security Server is registered on the network, you can begin exposing services to other participants or consuming theirs.
See: How to Publish a REST API or Consumption and/or Provision of Data Services
6. Validate¶
Exchange test messages with other participants on the ADEL network to validate connectivity, authentication, signing, and service access rights end-to-end.
Contacts¶
- ADEL Technical Support: adel@isaa.am