1.0.0
SPAR Release Notes for 1.0.0
Last updated
Was this helpful?
SPAR Release Notes for 1.0.0
Last updated
Was this helpful?
SPAR Release 1.0.0 represents a fully functional ID Account Mapper (one of the components of the DPI building blocks) as articulated by the In addition to the ID Account Mapper, the SPAR Release 1.0.0 also includes a Self Service module, using which, beneficiaries can login themselves into the SPAR Self Service system and maintain (link, unlink & modify) a mapping between their IDs and their Financial Address (Bank Accounts, Mobile Wallets).
The SPAR subsystem has 3 components, viz. openg2p-spar-mapper-api, openg2p-spar-self-service-api & openg2p-spar-self-service-ui. The features provided by these components are listed below
link, unlink, update and resolve REST APIs as specified by the G2PConnect specifications
Static persistence for Banks & Wallet Service Providers to facilitate self service maintenance of Account (Financial Address) in the Mapper
link, unlink, update and resolve REST APIs from a self service perspective - Consumed by the UI layer
link, unlink, update and resolve - Integration with mapper-api using G2PConnect APIs - Consuming the Mapper APIs
Integration with OIDC-OAuth2.0 based Login Providers with a Functional (or Foundational National ID)
A simple user-friendly UI to facilitate beneficiaries query the ID-Account-Mapper using their ID and displaying Financial Address (Account information) against the ID
UI layer to facilitate construction of Financial Address (based on the construction strategy) using the Bank Codes, Branch Codes, Wallet Service Provider Codes etc.
Login using OIDC-OAuth2.0 based Login Providers like E-Signet, Keycloak etc.
SPAR source code
Packaged dockers
Deployment
Testing
Test coverage reports
Documentation
API reference
Release 1.0.0 has been tested with limited scale. Load testing and performance benchmarks are planned for Release 1.1.0
To deploy this release on Kubernetes refer to the .
REST API security for Mapper APIs (openg2p-spar-mapper-api) - While the self-service-apis are secured using Auth tokens (from OIDC-OAuth2.0 Login Providers), the mapper-apis will need a JWS Token based authorization for partner systems. This has been described .
You can find the full list of Jira issues/backlogs .