Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
77 changes: 77 additions & 0 deletions content/en/docs/Release-Notes/420_openbanking_relnotes.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,77 @@
---
title: "Open Banking 4.2.0 Release Notes"
linkTitle: "Open Banking 4.2.0"
weight: 12
date: 2026-05-14
---

This update introduces two key areas of improvement:

* **Consent Admin Dashboard Enhancements**: A new `filterBy` query parameter has been introduced across the Core Consent API, Participant Management Admin API, and Participant Management User API, enabling dynamic filtering of consents by metadata fields and identity attributes using dot notation. This is complemented by an Advanced Search component in the dashboard UI, along with additional capabilities including an Additional Information tab for consent metadata, a consent details download button, a configurable Resource Owner filter, newest-first consent ordering, and system-aware timestamps.

* **Well-Known Endpoint Updates**: The endpoint response now correctly reflects mTLS port aliases introduced in Fusion v1.13, and internal scopes have been removed to expose only externally relevant scopes.

## Advanced Consent Search (`filterBy`)

This release introduces a dynamic `filterBy` query parameter across the consent APIs, enabling API consumers and administrators to search consents by metadata fields and mapped identity attributes—without relying solely on fixed query parameters.

**Supported syntax:**

```
filterBy=<fieldName>=<value>&<fieldName2>=<value2>
```

* Nested field support via dot notation: `metadata.externalIds.rcifId=12345`
* Only `AND` conditions are supported (using `&`)
* `OR` and `IN` operators are not supported in this release
* Invalid format returns `400 Bad Request`

**APIs updated:**

| API | Endpoint | Change |
|-----|----------|--------|
| Core Consent API | `GET /consents` | New `filterBy` query parameter |
| Participant Management Admin API | `GET /consents` | New `filterBy` query parameter |
| Participant Management User API | `GET /consents` | New `filterBy` query parameter |

## Consent Admin Dashboard Enhancements

### Advanced Search Component

A new **Advanced Search** field has been added to the Consent Admin Dashboard left panel, allowing users to search consents using the `filterBy` format directly from the UI. The searchable fields are configurable and managed through the dashboard configuration.

### Additional Information Tab

A new **Additional Information** tab is now displayed on the consent details page. This tab presents configurable metadata fields—such as bank-specific identity attributes (for example, `rcifId`)—associated with each consent record.

Configuration is managed via the environment property:

```
CONSENT_ADDITIONAL_INFO_FIELDS=metadata.rcifId,partner.name
```

### Download Consent Details

A **Download** button has been added to the consent details page. Clicking the button downloads a JSON file containing the full consent record.

### Configurable Resource Owner Field

The **Resource Owner** filter field on the Consent Admin Dashboard is now fully configurable and can be managed through the dashboard configuration.

### Consent List Sort Order

The consent list is now sorted in **descending order** (newest first), making it easier for administrators to quickly access the most recent consent records.

### System-Aware Timestamps

All timestamps displayed in the Consent Admin Dashboard now follow the **system time** of the hosting environment, ensuring consistency with the local time zone configuration.

## Well-Known Endpoint Updates

### mTLS Endpoint Aliases

The well-known endpoint response has been updated to correctly reflect the separate mTLS port introduced in Fusion v1.13. The `mtls_endpoint_aliases` object now contains URLs using the dedicated mTLS port, while all other endpoint URLs use the standard API port.

### Internal Scopes Removed

Internal scopes have been removed from the well-known endpoint response, ensuring only externally relevant scopes are exposed to API consumers and third-party providers.
Loading