Access token manager

This article relies excessively on references to primary sources. Please improve this article by adding secondary or tertiary sources. Find sources: "Access token manager" – news · newspapers · books · scholar · JSTOR (March 2024) (Learn how and when to remove this message)

In computer security, OpenHarmony Access token manager (ATM) is a component that facilitates unified application permission management based on access tokens within the OpenHarmony ecosystem that is used in OpenHarmony-based operating systems, Oniro OS distros and HarmonyOS with HarmonyOS NEXT iteration.^[1]

It is built upon access tokens and serves as a centralized mechanism for managing app permissions. Access tokens encapsulate essential information about an app

• App ID: Identifies the app.
• User ID: Associated with the user.
• App APL (Ability Privilege Level): Determines the app’s privilege level.
• App permissions: Specify what resources and functions the app can access.

Each app’s access token is uniquely identified by a 32-bit device-specific token ID.^[2]

Implementation

Developers utilize the ATM to handle permissions effectively. In certain scenarios, an app may require access to additional data or system functions beyond the default permissions. The ATM enables fine-grained control over permissions, allowing apps to access extended features when needed.

• App APL: Determines the app’s overall privilege level.
• ACL (Access Control List): Defines specific permissions for resources.
• Authorization Processes: Govern how permissions are granted.[6]

See also

• Access-control list
• Cacls
• Capability-based security
• C-list
• Confused deputy problem
• DACL
• Extended file attributes
• File-system permissions
• Privilege (computing)
• Role-based access control (RBAC)

References