SahamatiNet
  • Background
  • SahamatiNet POC
    • Introduction
    • Applications
    • Observability
    • Integration Steps
      • Sandbox Onboarding
      • IAM APIs
      • CR APIs
      • Integration with Router
        • Sample Code Snippets
          • Python
          • Java
          • JavaScript
          • GoLang
          • C#
        • Router APIs Specifications
          • FIU API Specification
          • AA API Specification
          • FIP API Specification
      • ReBIT Workflows using Router
        • Account Discovery & Linking
        • Consent Workflow
        • FI Request Workflow
    • Integration with Simulators
      • AA Simulator
      • FIP Simulator
      • FIU Simulator
    • Validation of Integration
  • Glossary
  • Guidelines
  • Frequently Asked Questions
  • How To Guides
    • How To Onboard to Sandbox ?
    • How To Decide on an Entity ID ?
    • How To Generate a Certificate ?
    • How To Generate Tokens ?
Powered by GitBook
LogoLogo

Copyright © 2025 - Sahamati Foundation

On this page

Was this helpful?

Export as PDF

Release Calendar

Was this helpful?

AA Ecosystem Release Calendar by Sahamati

The Release Calendar outlines the updates and improvements introduced by Sahamati in the common services provided to the Account Aggregator (AA) ecosystem. It highlights key feature deployments and their scheduled timelines for both UAT and Production environments, enabling participants to stay aligned with regulatory and ecosystem-related enhancements. By adhering to the deployment dates, participants can seamlessly integrate these updates into their own release cycles, ensuring they stay up to date with the evolving changes.

2024 - Q4

Release Item
Description
Details

Customisable Client Secret Expiry Duration

Ecosystem members can specify the expiry duration for secrets' rotation within regulator-defined boundaries.

Members can set expiry duration value via the API request, with a default value of 180 days or a customised value using the secretExpiryDays parameter defined by the entity itself.

Grace Period for Expired Secrets

A grace period allows access token generation with expired secrets, accompanied by a warning.

Tokens can still be generated during the 5-day grace period after expiry, with a warning that the secret has expired.

Error Reduction in Automated Secret Reset

Changes to reduce errors in the automated secret reset process, even if environment configurations change.

Reduces errors during the secret reset process, ensuring compatibility with updated expiry durations or other configuration changes.

Human Readable Expiry Date Format

The expiry date is now visible in a human-readable ISO format.

The expiry date is now provided in the response attribute expirationDate along with expiresOn in the secret API, formatted in an easily readable ISO format.

For detailed information on the API changes, do refer to the API documentation

2024 - Q3

Description
UAT Status
Production Status

Deployed (August 2024)

Deployed (Oct 2024)

Deployed (August 2024)

Deployed (Oct 2024)

Deployed (July 2024)

Deployed (Oct 2024)

Update on Client Secret Rotation:

Based on the UAT feedback regarding client secret rotation, we will be updating the validity period for newly generated tokens to 180 days. As a result, the planned deployment, originally scheduled for 3rd October 2024, has been deployed on 16th October 2024, following the next round of UAT.

The next release will also include changes that allow entities to parameterise and configure the expiry period themselves, based on their respective regulatory guidelines.

link here
Deprecation of V1 API Endpoint URLs in Base URL of Entities in Central Registry
Client Secret Rotation for Participants in Token Service (Identity & Access Management)
Deactivation of deprecated V1 APIs of Central Registry