Purpose
This page summarizes the NRDEX exchange environments in the same comparison style commonly used for X-Road environment documentation.
NRDEX currently documents a test environment for member onboarding and a production environment for approved live data exchange. Environment identifiers are case-sensitive and must be used exactly as issued in certificates, member registrations, and configuration.
Environment comparison
| Property | NRDEX-PROD (production) | BD-TEST (test) |
|---|---|---|
| Environment identifier | NRDEX-PROD |
BD-TEST |
| Primary purpose | Live inter-agency and authorized institutional data exchange | Integration testing, onboarding rehearsal, service validation, and member readiness checks |
| Real data used | Yes, subject to approved legal basis, access grants, and production controls | No. Test or masked data should be used unless separately approved |
| Members | Approved production members | Prospective members and approved test participants |
| Service publishing | Production services only after governance, legal, and technical approval | Test services for integration validation and acceptance testing |
| Access control | Explicit access grants between approved production members | Explicit test access grants between approved test participants |
| Certificate use | Production SIGN and AUTH certificates | Test SIGN and AUTH certificates |
| Security Server requirement | Required for every participating organization | Required for every participating organization testing through NRDEX |
| Hardware signing device | by the governing authority and certificate policy | by the governing authority and certificate policy |
| Onboarding channel | NRDEX governing authority and production onboarding process | NRDEX onboarding process and technical coordination |
| Service level | Production service level and incident process apply | No production service level unless explicitly agreed |
Technical properties
| Property | NRDEX-PROD (production) | BD-TEST (test) |
|---|---|---|
| Configuration anchor | To be published for production onboarding | Anchor File for BD-Test Environment |
| Configuration download URL | https://test-cs.nrdex.gov.bd/internalconf |
|
| Fallback configuration download URL | http://test-cs.nrdex.gov.bd/internalconf |
|
| Central Server host | test-cs.nrdex.gov.bd |
|
| Monitoring server | ||
| Member classes | by NRDEX governance | by NRDEX governance |
| Certification service provider | by certificate policy | by certificate policy |
| Timestamping service provider | by certificate policy | by certificate policy |
| Global configuration validity | Defined by the published global configuration | |
| OCSP validity | Defined by the published global configuration | |
| Timestamping interval | Defined by the published global configuration | |
| Federated environments |
Usage guidance
- Use
BD-TESTbefore production onboarding to validate Security Server installation, subsystem registration, service descriptions, access grants, and request handling. - Keep certificates, subsystems, service descriptions, and access grants separate between test and production.
- Do not reuse production datasets in the test environment unless the data has been approved, masked, or otherwise handled under the applicable data protection requirements.
- Treat environment identifiers as case-sensitive protocol values.
- Move to
NRDEX-PRODonly after the member organization, services, access conditions, and technical readiness have been approved.
Maintenance note
The BD-TEST values on this page are based on the published NRDEX test configuration anchor in this repository. Production values and detailed certificate policy fields should be updated when the governing authority publishes the corresponding production configuration and operating policy.