Skip to content

Joining ADEL

High-level steps to onboard your organization onto the Armenian Data Exchange Layer (ADEL) X-Road network.

Test instance only

This guide currently covers onboarding to the ADEL test instance, intended for development, integration, and pre-production validation. Steps and contact points for the production environment will be published separately once the production onboarding process is finalized.

Steps

1. Request test access

Contact ISAA to register your organization on the ADEL test network and to receive the artifacts required for configuration:

ISAA will provide:

  • Configuration anchor for the ADEL
  • 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 22.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 test network

Using the configuration anchor and member code provided by ISAA:

  1. Upload the anchor and perform initial configuration
  2. Activate soft tokens and add the timestamping service
  3. Generate CSRs for authentication and signing certificates
  4. Upload the issued certificates and register the authentication certificate
  5. Create your first subsystem and submit the registration request to the test Central Server

See: Security Server Configuration Guide

5. Publish or consume services

Once your Security Server is registered on the test network, you can begin exposing services to other test participants or consuming theirs.

See: How to Publish a REST API

6. Validate

Exchange test messages with other participants on the ADEL test network to validate connectivity, authentication, signing, and service access rights end-to-end.

What is not covered here

Production onboarding will additionally involve membership agreements, SLAs, formal compliance review, production certificates, and registration on the production Central Server. Those steps are out of scope for this page and will be documented separately.

Contacts