v8.6.7

Multitenancy support

• The Operator onboarding process is now defined in two distinct steps: 
  • Tenant creation. 
  • Operator or SCA (Supply Chain Admin) creation.
• The onboarding process executes asynchronously, and ASIK handles the creation process.
• After a tenant is created or onboarded, each API call to the ASIK service is modified to include the user-id and tenant-id in the call headers.
• The data in the blockchain is stored tenant-wise, and each tenant has its dedicated chaincode on the blockchain.
• Flexible tenant creation: user can provide peer type, peer region & server type. Tenant creation is now an automated process, saving time and simplifying the process.
• Tenants are deactivated without manual intervention (but data will persist for the tenant). After a certain period, if a tenant is permanently de-boarded, only data clean-up activity is required.

Secure Webhook Credentials 

• Webhook credentials are now stored in encrypted form instead of plain text format.
• Existing webhook credentials are also migrated in encrypted format for future use. 

 Improved User Data Management

• Enterprises can make configurations such as:
  • Select data storage – whether in a shared environment or a dedicated environment, providing flexibility and control.
  • Select the number of data source points for respective data storage.
  • Provide the region where the data will be stored.
• Addition of User IDs instead of User card names.
• Support of multiple accounts for the same user.
• There is no overhead for integrating services to maintain the mapping of User Id and Card Name.
• Migration of users and data involves fewer manual interventions.

Improved CPU core usage

• CPU usage is now optimized, using PM2/cluster modes or alternate configurations to offer superior platform performance.

Graceful start

• After a service is deployed to the server, the APIs will only start taking requests once all connections have been successfully established (DB, Queues, and ASIK Connections).