🕐Obsolete Guardian Artifacts

This section provides comprehensive information on handling obsolete Guardian artifacts within the Managed Guardian Service (MGS).

What Are Obsolete Guardian Artifacts?

Obsolete Guardian artifacts are components within the MGS that become outdated or invalid due to system changes, particularly the periodic resets of the Hedera Testnet. This does not apply to Mainnet as there are no resets on Mainnet. These artifacts include, but are not limited to, policies, schemas, tokens, and Hedera account IDs. The Testnet resets aim to improve the overall performance and security of the platform, but they also result in the removal of existing artifacts.

Types of Obsolete Artifacts:

1. Policies:

   • These are sets of rules and configurations that govern the behavior and operations of the Guardian within a tenant. Policies define access controls, operational procedures, and compliance requirements. When these become obsolete, they should be exported and then re-uploaded or recreated.

2. Schemas:

   • Schemas represent the structured data models used within the Guardian system. They define how data is organized, validated, and processed. Upon testnet reset, these schemas are deleted and need to be re-established.

3. Tokens:

   • Tokens within the Guardian system are used for representing environmental digital assets. Obsolete tokens need to be reissued or recreated after a reset.

4. Hedera Account IDs:

   • These are unique identifiers associated with user accounts on the Hedera network. When the testnet resets, these account IDs are deleted and must be recreated to restore user functionality.

Impact of Obsolete Artifacts:

• Data Loss:

  • If artifacts are not exported before a reset, there is a risk of permanent data loss. It is essential to back up all necessary data before the reset occurs. MGS offers the ability to store all necessary data for up to 30 days post Testnet reset.

• Functional Disruption:

  • Users will experience disruptions in their operations until the artifacts are recreated and the system is fully reconfigured.

Preventive Measures:

• Regular Backups:

  • Schedule regular exports of critical policies, schemas, and other artifacts to ensure that data is backed up and can be restored when needed.

• Stay Informed:

  • Keep up-to-date with announcements regarding Testnet resets and other significant changes. This allows for timely preparation and action to mitigate the impact of obsolescence.

• Effective Communication:

  • Maintain clear communication channels with all users, particularly regarding the steps they need to follow during and after resets or significant system changes.

Impact of Hedera Testnet Resets

When the Hedera Testnet is reset:

• All Guardian artifacts within your tenant (e.g., policies, schemas, tokens, Hedera account IDs) are deleted within 30 days of the reset.

• Standard registries and tenant admins have the ability to export and import these artifacts within 30 days of the reset.

• Policy users (non-admins) will retain login access but lose functionality until reconfiguration is complete. Please see "Process for Testnet Resets."

Roles and Responsibilities

• Standard Registries:

  • Can export policies, schemas, and other artifacts before a testnet reset.

  • Responsible for re-uploading or recreating these artifacts after a reset.

• Tenant Admins:

  • Can delete users and tenants.

  • Responsible for reconfiguring the tenant and inviting users back into the system.

• Policy Users:

  • Do not have export functionality.

  • Will need to contact their tenant admin to regain access to Guardian functionalities after a reset.

Steps to Handle Obsolete Guardian Artifacts

1. Before the Reset:

   • Export Artifacts: Standard registries should export all necessary policies, schemas, tokens, and Hedera account IDs.

   • Notify Users: Inform all policy users about the upcoming reset and their need to contact tenant admins post-reset.

2. After the Reset:

   • Reconfigure Tenant: Tenant admins must reconfigure the tenant in MGS.

   • Re-upload Artifacts: Standard registries should re-upload or recreate the necessary policies, schemas, tokens, and Hedera account IDs.

   • Resend Invites: Tenant admins need to resend invitations to policy users to restore their access to the system.

Support and Assistance:

If you have any questions or need assistance, please do not hesitate to contact your tenant admin or our support team at [e-mail].