Skip to content

Release 2.7.7

We’re excited to announce the release of version 2.7.7!

Overview

This release introduces significant enhancements to Federated ID Management, focusing on:

  • Improved API capabilities
  • Enhanced data security
  • Streamlined bulk operations

🚀 New Features & Enhancements

🔗 Bank Account Linking via API

Support for linking Bank Account Numbers and ABA Routing Numbers via new API endpoints.

🛡️ Federated ID Management Module

Introduction of a dedicated Federated ID Management module with Role-Based Access Control (RBAC) to ensure secure and granular access.

🧑‍💼 Admin UI Enhancements

New UI screens enabling Platform Admins to manage Federated IDs directly through the interface.

🔧 Backend Integration

Backend services implemented to support the Federated ID lifecycle.

🔗 Federated Linking Enhancements

Linking of Federated Names and Wallet Addresses with bank account numbers for unified identity handling.

🔍 Bank Account Details Retrieval

New API to fetch linked bank account details using either a Federated ID or a Wallet Address.

🔐 Data Encryption

Encryption of bank account numbers in the database to ensure the protection of Personally Identifiable Information (PII).

Note: Consider aligning with standards like PCI DSS, GDPR, or SOC 2, depending on your compliance goals.

📂 Bulk Upload Support

CSV-based bulk upload functionality for managing: - Federated IDs
- Wallet Addresses
- Bank Account Numbers
- ABA Routing Numbers

🛡️ Security and Compliance

  • Encryption of sensitive data (e.g., bank account numbers) has been implemented at the database level to comply with data protection standards. (Consider specifying applicable standards, e.g., PCI DSS, GDPR, if relevant.)

Upgrade Notes

The sequence of steps to follow to upgrade are:

  1. Container images and configmaps
  2. DB migrations
  3. Swagger APIs

Container images and configmaps

All provided images, available in the Image List section should be downloaded and built to be LGPL compliant.

All new images tags will be used to update Kubernetes manifests.

Core microservice

ConfigMap

Add/replace the following values in Core microservice's ConfigMap:

configmap.yml
CSV_STORAGE_ACCOUNT_CONNECTION_STRING: '[replace with storage connection string]'
CSV_CONTAINER_NAME: 'bank-acounts' [create a new container]
AZURE_STORAGE_ACCOUNT_KEY: '[replace with storage account key 1]'
AZURE_STORAGE_ACCOUNT_NAME: '[replace with storage account name]'

DB migrations

Download DB migrations ZIP file available in Assets, unpack/unzip it in order to perform remaining instructions.

DB backup

Before proceeding with remaining steps, it's strongly advised to take a database backup before proceeding.

Update credentials

Edit/create a file named development.env inside db-migrations/src/common/envs folder

db-migrations/src/common/envs/development.env
DB_HOST=[replace with db host url]
DB_USER=[replace with db user]
DB_PWD=[replace with db user password]
DB_NAME=[replace with db name]

AZURE_TENANT_ID=[replace with azure tenant id]
AZURE_CLIENT_ID=[replace with azure client id]
AZURE_CLIENT_SECRET=[replace with azure client secret]
AZURE_KEYVAULT_NAME=[replace with azure keyvault name]

Execute DB migrations

Execute the remaining commands located inside the extracted content folder (e.g.: db-migrations):

Execute migrations
$ npm install
$ npm run migrate

Swagger APIs

Download Swagger APIs tarball file available in Assets, unpack/unzip it in order to perform remaining instructions.

Update API

omnumi-internal
Upload file
  1. Navigate to the API Management service service.
  2. Expand APIs left blade menu and select APIs
  3. Select omnumi-internal and expand the API option button (...) to select Import available option
  4. Select OpenAPI tile
    • Import method: Update
    • Select file: Omnumi-Internal-Api.json
Update settings

After a successful import update the following fields:

  1. Select omnumi-internal API again
  2. Open Settings tab and update Web service URL with ul-core microservice URL
  3. Save the changes
omnumi
Upload file
  1. Navigate to the API Management service service.
  2. Expand APIs left blade menu and select APIs
  3. Select omnumi and expand the API option button (...) to select Import available option
  4. Select OpenAPI tile
    • Import method: Update
    • Select file: Omnumi.public-api.json
Update settings
  1. Select omnumi API again
  2. Open Settings tab and update Web service URL with ul-core microservice URL
  3. Save the changes
Update methods chain-core
  1. Select omnumi API again
  2. Open Design tab and enable Group by tag
  3. On the list expand ChainCore and update the Backend - HTTP(s) endpoint with ul-chain-core microservice URL
  4. Repeat operation for all listed API methods on the ChainCore

Image list

Microservice name Image tag
Core Microservice omnumisandbox.azurecr.io/core:2.7.7-deliverable
Frontend Microservice omnumisandbox.azurecr.io/frontend:2.7.7

Assets

Login into files portal