- chore(dataspace): remove legacy host and -mgmt participant contexts (#3857)latest12Docsce123702026-10-02 21:23
Change detail
35e400c8dd72 → 53cac00998e6 · 3 changes across 1 operation
- GET/dataspace/provisioning-status
- ●
added the new
SYSTEMenum value to the//response property for the response status - ○
removed the
HOSTenum value from the//response property for the response status - ○
removed the
MANAGEMENTenum value from the//response property for the response status
- ●
Change detail
6fe24a40dfc9 → 35e400c8dd72 · 4 changes across 2 operations and 1 section
- GET/system/property
- ▲
api path removed without deprecation
- ▲
- PATCH/system/property
- ▲
api path removed without deprecation
- ▲
- components
- ○
removed the schema
- ○
removed the schema
- ○
Change detail
f27f379b2dba → 6fe24a40dfc9 · 3 changes across 3 operations
- GET/dataspace/provisioning-status
- ○
removed the
SYSTEMenum value from the//response property for the response status
- ○
- GET/system/property
- ○
endpoint added
- ○
- PATCH/system/property
- ○
endpoint added
- ○
- feat(dataspace): provision the SYSTEM participant on every Security Server313Docs1fb88bc2026-09-08 13:22
Change detail
8af364b0559f → f27f379b2dba · 7 changes across 4 operations and 1 section
- GET/dataspace/tls-certificate/enrollment-status
- ▲
api path removed without deprecation
- ▲
- GET/system/property
- ▲
api path removed without deprecation
- ▲
- PATCH/system/property
- ▲
api path removed without deprecation
- ▲
- components
- ○
removed the schema
- ○
removed the schema
- ○
removed the schema
- ○
- GET/dataspace/provisioning-status
- ●
added the new
SYSTEMenum value to the//response property for the response status
- ●
- refactor(ds-identity): say bound, not pinned, for a participant's recorded identity11Docs38e240d2026-09-02 10:25
Change detail
2086ddf22174 → 8af364b0559f · 2 changes across 1 operation
- GET/dataspace/provisioning-status
- ●
added the new
MEMBERenum value to the//response property for the response status - ○
added the optional property
//to the response with the status
- ●
- feat(security-server): detect identity-hub DID drift before provisioning1Docs231ca602026-08-28 09:24
- refactor(security-server): make the provisioning reconciler read-only over ds_participant pins12Docs1cf9bfa2026-08-28 08:26
- feat(security-server): provision one dataspace participant context per hosted member13Docs0ca14f82026-08-12 13:55
- Merge branch 'develop' of https://github.com/nordic-institute/X-Road into XRDDEV-25334Docs38e99b32026-07-15 13:27
- Merge branch 'develop' of https://github.com/nordic-institute/X-Road into XRDDEV-25331Docs3be11432026-07-08 06:39
- feat: Fix querying for configuration properties with scope, refactoring11Docs7eb82562026-03-25 08:59
- feat: Implemented endpoints in order to retrieve and update configurable properties2Docs28e97b42026-03-09 11:58
- feat: Add input validations to central and security servers description fields261612Docs24bb6632026-01-14 15:31
- feat: select csr format based on global configuration value (#3147)231612Docs955a4dd2025-12-05 15:46
- feat: add support for testing connections to other security servers on the diagnostics page (#3103)261619Docs7efa7692025-12-02 05:43
- feat: As a Security Server Administrator I want to be able to define what policy is used for choosing TSA-s and OCSP responders so that I can better manage costs191510Docs0e5c30e2025-11-07 15:03
- feat: add the central server connection test to diagnostics page (#3001)14Docs9cff8c22025-10-27 09:37
- feat: As a Security Server Administrator I want the diagnostics information available for global configuration and TSA to be improved so that I can more easily figure out issues with it49Docs38bae662025-09-23 14:43
- chore: Add input validation when creating user or changing password + introduce the option of strong password policy enforcement (#2870)2Docsb2bb2202025-07-01 11:30
- feat: Introduce database based authentication for containerized deployment (#2845)22Docs3000d5c2025-06-20 06:26
- feat: As a Developer I want to add the capability of sharing operational monitoring data with the rest of the components via gRPC to the operational monitoring addon so that we can use it to visualise1Docs20b4a072025-05-28 14:55
- feat: As a Developer I want to rework the ACME notifications display structure in the diagnostics view as it is becoming a mess31Docsdfe69312025-04-28 21:24
- feat: As a Security Server Administrator I would like to be able to see the memory usage of the proxy component in the diagnostics page so that I can visually see what the current usage is1Docs802bc292025-03-28 14:25
Revisions go back to the API's first capture.