Protecting Asset Data

NOTE

The asset data mentioned in this topic refers to sensitive data, including passwords, login tokens, and other critical data (such as credit card numbers).

When to Use

Asset Store Kit (ASSET) is used in the logins of the users who select Remember password on the login page. The application/browser stores the user passwords in an asset store, which ensures the password security.

When a user opens the login page again, the application/browser obtains the user password from the asset store and automatically fills the password in the Password text box. The user only needs to tap the Log In button to complete the login.

Development Process

The following figure illustrates the development process for using Asset Store Kit to protect the passwords (hereinafter referred to as assets).

1. The service queries an asset and determines whether the asset exists in the asset store based on the query result.

   • For details about the development procedure, see Querying Assets (ArkTS)/Querying Assets (C/C++). For details about the sample code, see Querying Attributes of an Asset (ArkTS)/Querying Attributes of an Asset (C/C++).

2. If the asset does not exist:

   • Add an asset. For details, see Adding an Asset (ArkTS)/Adding an Asset (C/C++).

3. If the asset exists, the service can perform any of the following operations based on service requirements:

   • Remove the asset. For details, see Removing Assets (ArkTS)/Removing Assets (C/C++).
   • Update the asset. For details, see Updating an Asset (ArkTS)/Updating an Asset (C/C++).
   • Query the plaintext of the asset. For details, see Querying Assets (ArkTS)/Querying Assets (C/C++). For details about the sample code, see Querying the Plaintext of an Asset (ArkTS)/Querying the Plaintext of an Asset (C/C++).