v8.7.0

更新日 30 May 2022
2 読む分

印刷する
共有
闇
光
PDF

The content is currently unavailable in Ja - 日本語. You are viewing the default English version.

記事の要約

この要約は役に立ちましたか?

ご意見ありがとうございます

Enhancements in this Release v8.7.0

May 30^th, 2022 Version 8.7.0

The DL Asset Track platform now supports multitenancy, meaning a single instance can serve multiple users. This release has significantly improved the Operator onboarding process, and now each Operator is associated with a tenant.

All activities performed by Data Operators, Subordinates, and Participants under an assigned Operator are stored and tracked on the blockchain separately. This segregation is classified based on the corresponding tenant. All activities carried out by Data Operators, Subordinates, and Participants under the supervision of an assigned Operator are recorded and tracked separately on the blockchain.

Additionally, the DL Asset Track platform has a security update. All the existing webhook credentials stored in the database are encrypted. The enhancements in the code base now enable the platform to save the webhook credentials in encrypted form for any future use.

Updates for ASIK

Multitenancy support is enabled in ASIK Track.
Clients can interact with the system using only User IDs, not User Card Names.
Support for two fabric versions, i.e., Fabric 1.x and Fabric 2.x.
Secure connection with external services like Kafka, PostgreSQL, Redis, etc.

Features Delivered in this Update

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.

For any questions, please email us at dl.releasenotification@dltlabs.io

この記事は役に立ちましたか?

What's Next

v8.6.0