Skip to main content

Release Notes

Full changelog for all Raidiam Connect versions.

⚠️

Upcoming Breaking Changes

Future changes that may require action on your end. Review and plan ahead.

"Withdrawn" status renamed to "Inactive" across Organisations, Servers, and Applications

Q3 2026

The Withdrawn status value for Organisations, Authorisation Servers, and Applications will be renamed to Inactive. This is a nomenclature change only — the behaviour and meaning of the status remain unchanged.

A transition period of approximately 3 months will be provided before the change takes effect. Any integration that reads or compares the status value as a string should be updated to handle Inactive in place of Withdrawn.

Organisation certificate update removed in favour of key-material API

v3.0.0Q3 2026↓ Download Swagger

The ability to update an organisation certificate's description has been removed. The PUT endpoint for updating organisation certificate details by type is no longer available.

Removed capability:

  • PUT /organisations/{OrganisationId}/certificates/{OrganisationCertificateType} — updating certificate description
Note: Certificate revocation remains available via PUT /organisations/{OrganisationId}/certificates/kid/{CertificateOrKeyId}.

To manage certificates going forward, use the new key-material API introduced in this release:

  • GET /organisations/{OrganisationId}/key-material — list key material
  • POST /organisations/{OrganisationId}/key-material — create new key material
  • GET /organisations/{OrganisationId}/key-material/{KeyMaterialID} — retrieve a specific item
  • PUT /organisations/{OrganisationId}/key-material/{KeyMaterialID} — update or revoke a key material item
  • GET /organisations/{OrganisationId}/key-material/{KeyMaterialID}/attachments — list attachments
  • POST /organisations/{OrganisationId}/key-material/{KeyMaterialID}/attachments — add an attachment
  • PUT /organisations/{OrganisationId}/key-material/{KeyMaterialID}/attachments/{KeyMaterialAttachmentID} — update an attachment
Note: All existing keystore endpoints will be fully preserved.
Compare versions:→

2.5.0#

Latest↓ Download Swagger▾

This release introduces expanded search, filtering, and sorting capabilities across core directory resources, new scope and access control options for programmatic client management, and enhanced document handling workflows. It also delivers interface improvements including unified document views and sortable audit tables, alongside fixes addressing form validation, permission consistency, and document status handling.

New features#

New scope for cross-client application and certificate management

New Feature

A new scope, directory:software:organisation:application:management, allows a software client to programmatically create, update, suspend, and delete other clients within the same organisation.

  • Used alongside the existing certificate management scope, this enables representative organisations to automate onboarding of beneficiary clients and their associated transport and signing certificates via API
  • No platform intervention required

Enhancements#

Expanded filtering, sorting, and search across directory resources

Enhancement

Multiple directory API endpoints now support filtering, sorting, and partial-match search. Multiple filter parameters can be combined simultaneously using AND logic.

Organisations — filter by flag, T&C signing status, segment, and size; sort by name, ID, and creation date

Contacts — filter by contact type and department; sort by contact type and email; search by email, phone, and contact ID

Authority claims — filter by role, status, and authorisation domain; sort by domain, role, and status

Authority domain claims — filter by status; sort by authority name; search across authority name, domain name, and claim ID

Domain users — filter by status, system contact role, and notes; sort by status, role, and email; search by user ID and email

API resources — filter by API version, family completeness, API family type, status, and certification status

Authorisation server certifications — filter by status, certification status, profile type, and profile variant; sort by certification dates and profile version

Applications (software statements) — filter by status, locked state, flag, OpenID Federation enablement, and signed request object requirements; sort by status, name, and creation date

Application certifications — filter by status, profile variant, and profile type; sort by certification dates and profile version

Application roles — filter by role, status, and authorisation domain; sort and search by role

Organisation and application certificates — filter by status and key type; sort by status, validity dates, and key type; search by key identifier

Organisation administrators — filter by status; sort by status and email; search by email address

Unified view for documents signing and history

Enhancement

The Documents page now presents a single scrollable view replacing the previous two-tab layout.

  • Pending signatures and signing history are displayed together in collapsible accordion sections
  • Reduces navigation steps for users managing platform documents
Unified view for documents signing and history

Column sorting now available in audit tables

Enhancement

Users can now sort audit table columns directly from the UI.

  • Sorting controls follow existing design guidelines and are available across audit views

Bug fixes#

Sign button error on deleted documents resolved

Bug Fix

Users attempting to interact with a document in Deleted status could encounter a misleading error stating that other requests must be in a terminal state before signing.

  • The sign action is now correctly blocked for documents in Deleted status
  • The misleading error is no longer presented to users

Enforce domain status when adding authority role claims

Bug Fix

The API now correctly validates both the domain status and the role status before allowing a role claim to be added to a software statement or application.

  • Roles can no longer be added or re-enabled under an inactive domain claim
  • A data migration corrects existing records where role claims or domain users were left active under inactive domains

Organisation search clear button and 'only my organisations' filter fixed

Bug Fix

Two issues with the Organisations search bar have been resolved:

  • The clear (X) button is now always visible when the field contains text, rather than only appearing on hover
  • Searching while the 'Only my organisations' filter is active no longer resets the filter — results remain correctly scoped to the authenticated user's organisations

T&Cs signers dropdown reflects actual signer count

Bug Fix

The signatories dropdown in the Terms and Conditions signing dialog now displays only the number of signers configured for the document, rather than always showing four options.

  • When only one signer is available, the dropdown is disabled and pre-populated with the value 1

Invalid page size value now handled correctly on clients endpoint

Bug Fix

The clients endpoint previously returned all records and an incorrect negative total page count when a page size of -1 was supplied.

  • Validation has been updated so that invalid page size values are handled consistently
  • Invalid values are rejected with an appropriate error response

Federation entity management type field now selectable

Bug Fix

The 'Federation Entity Management Type' field is now correctly available and selectable when converting an application from non-federated to federated.

  • Previously the field was either absent or the form could be saved without a valid selection, causing an API validation error

Reference data flags created date now correct

Bug Fix

The 'Created At' column in the Reference Data Flags table now displays the actual creation timestamp returned by the API.

  • Previously all entries incorrectly showed the current date regardless of when each flag was created

Token endpoint no longer returns 500 on account lookup errors or short credential values

Bug Fix

Two issues with the token endpoint have been resolved:

  • The JWT bearer grant handler now correctly catches errors during account lookup, returning a proper error response instead of an unexpected 500 status
  • A runtime error causing Lambda invocation failures when client_secret or authorisation code values were shorter than 8 characters has been resolved — the /token endpoint now processes short credential values without throwing an invalid count error

2.4.0#

▾

2.3.0#

▾

2.2.0#

▾

2.1.0#

▾

2.0.0#

▾