Page Comparison

...

1. OIDF Federal Software Statement Integration:

   • Support for OIDF Federal Client creation process has been added to the OFTF. As part of this, the TPP registration process has been updated to include a call to the Open Finance Trust Framework (OFTF) using the Federated Client ID (a URL).

2. Healthz Endpoints:

   • Enhanced /healthz endpoints across all services to improve monitoring and diagnostics for system health.

3. Support for PEM and JWE Formats:

   • Users can now configure JWT authentication using PEM and JWE formats, providing greater compatibility with widely-used cryptographic systems and enabling encrypted JWTs for enhanced security.

4. LFI Consent Status Update Notifications:

   • Added notifications for Consent Status updates across the following:

     • Bank Data Sharing Consents

     • Insurance Consents

     • Bank Service Initiation Consents

5. Insurance Specification Version Upgrade:

   • Upgraded the Insurance API specification to v1.2 to incorporate schema updates. The implementation is planned for the next release.

6. Simplification of ConsentExpiryCronJob Logic:

   • Improved query logic in ConsentExpiryCronJob to better handle CBUAE consents, ensuring more reliable expiration processing.

7. Direct Postman Environment Retrieval by Client ID

   • Introduced the ability to retrieve a Postman environment directly via an endpoint by providing the client ID as a query parameter, enabling seamless integration and faster setup.

4.2 Fixes

...

Fixed issue where Patch consent returned 404 instead of 400.

...

Corrected permissions for ReadPartyUserIdentity.

...

Refactored cron job to use MongoDB aggregations for filtering consents in specific scenarios.

...

Fixed Single Instant Payment (SIP) consent status update when '4xx' errors are returned by LFI.

...

Updated default PAR validity expiration time.

...

Resolved missing status in /consents/{consentId} response when called via Postman.

...

SDT-478 Resolved inconsistencies in the {{/consents/{consentId}}} endpoint behavior, including missing implementation for {{ReadPartyUserIdentity}} permissions and corrected data structure for {{creditor}} in {{AEPaymentConsentsPII}}.

SDT-671 Updated the POST Payments request in the E2E Postman collection to include the latest PII payload structure, ensuring compatibility with the latest API specifications.

SDT2-25 The problem where dates in the correct ISO 8601 format were causing errors has been fixed. Dates are now accepted and processed properly.

SDT2-29 The issue has been resolved, and the flow will now function smoothly.

SDT2-32 The issue issue is fixed by disabling the button as soon as it's clicked. This stops users from clicking it multiple times and ensures the action is completed correctly without any errors.

SDT2-33 The issue issue is fixed by disabling the button as soon as it's clicked. This stops users from clicking it multiple times and ensures the action is completed correctly without any errors.

4.3 Known Issues to be fixed in next release (12 Feb)

1. Status Change:
   Consent status is not turning to expired after the ExpirationDateTime has passed

2. ExpirationDateTime Logic for a Past Date:
   Consent getting created even if ExpirationDateTime is a Past Date for FILE PAYMENT

3. Validation of PII

...