All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Updated nuget package versions
- Migrated from .NET 6 to .NET 8
- Migrated docker compose from v1 to v2
- Removed Bank Participant Data scope (i.e. cdr-register:bank:read) references.
- Updated NuGet packages to avoid vulnerabilities.
- DCR and PAR screen defaults to Authorisation Code Flow (ACF).
- Fixed Consumer Data Sharing Common swagger proxy UI failure due to 'IndustryName' validation - Mock Data Recipient Issue 68
- Refactored code and minor bug fixes
- The address property in the userinfo endpoint structure is updated from string to object. Mock Data Recipient Issue 67
- Refactored code and fixed code smells
- Bug limiting the amount of DCR messages that can be queued. Sandbox Issue 31
- Regenerated all mTLS, SSA and TLS certificates to allow for another five years before they expire.
- redirect_uris and response_types in DCR request are now array of string.
- support for acr values
- Updated to be compliant with FAPI 1.0 phase 3.
- Dynamic Client Registration Azure Function updated to be compliant with FAPI 1.0 phase 3.
- Home page html content to reflect latest version
- Add body to post requests. Sandbox Issue 15
- Fixed data conversion error when saving Cdr Arrangement. Sandbox Issue 14
- Send redirect_uris as an array instead of string when performing background Dynamic Client Registration requests. Issue 50
- Changed CdrArrangement.ClientId database column data type from UniqueIdentifier to nvarchar(100).
- Intermittent issue where redirect_uri in consent and PAR JWT is null. Sandbox Issue 11
- mtls_endpoint_aliases not used as per RFC 8705 in PAR and token exchange. Sandbox Issue 12
- Logging middleware to create a centralised list of all API requests and responses
- Primary key constraints for registrations. Now combines Client Id and Data Holder Brand Id as the unique constraint.
- Updated arrangement revocation to match CDS v1.18. Configuration added based on the date to make functionality available or unavailable.
- Updated side menu layout and text on screens.
- Updated package references.
- Fixed issue with Dynamic Client Registration Azure function not retrying for DCR Failed data holders.
- Azure functions to perform Data Holder discovery by polling the Get Data Holder Brands API of the Register.
- First version of the Mock Data Recipient deployed into the CDR Sandbox.
- Build and Test action to archive test results. End to end tests now included in test report.
- PKCE support added to "Consent and Authorisations" and "PAR" in preparation for FAPI 1.0.
- Ability to connect and authenticate with data holders that have implemented either FAPI 1.0 Migration Phase 1 and Phase 2.
- Ability to connect to and test the Mock Data Holder Energy and other Energy Data Holders.
- Upgraded the Mock Data Recipient codebase to .NET 6.
- Replaced SQLite database with MSSQL database.
- Changed the TLS certificates for the mock data recipient to be signed by the Mock CDR CA.
- Extra steps detailed for using the solution in visual studio, docker containers and docker compose file.
- Use the latest endpoints from the Mock Register that support Banking, Energy and Telco as an industry.
- Quality of Life updates to assist with usability and testing.
- Regenerated all certificates to allow for another year before they expire.
- Banking API swagger in data sharing not displaying. Issue 30
- GitHub Actions Workflow for Build, Unit Test, and Integration Test project.
- GitHub Issue config with supporting links to CDR related information.
- Minor changes to pipeline appsettings files to support GitHub Actions.
- Minor changes to docker command in the ReadMe. Issue 25
- Fixed issue calling data holder resource APIs using data recipient proxy. Issue 26
- First release of the Mock Data Recipient.