mirror of
https://gitee.com/openharmony/useriam_user_auth_framework
synced 2024-12-04 22:27:12 +00:00
1c47881b69
Signed-off-by: lvshuai <lvshuai11@h-partners.com> Change-Id: Ib995110db1c6b088ee1df876a9837e10cf875d16 |
||
|---|---|---|
| common | ||
| figures | ||
| frameworks | ||
| interfaces/inner_api | ||
| param | ||
| sa_profile | ||
| services | ||
| test | ||
| user_auth_icon | ||
| .gitignore | ||
| bundle.json | ||
| cfi_blocklist.txt | ||
| CODEOWNERS | ||
| hisysevent.yaml | ||
| LICENSE | ||
| OAT.xml | ||
| README_ZH.md | ||
| README.md | ||
Unified User Authentication (userauth)
Introduction
As a basic component of the User Identity & Access Management (IAM) subsystem, Unified User Authentication (userauth) implements unified user authentication and provides biometric feature authentication APIs to third-party applications.
Figure 1 userauth architecture
The userauth APIs support user authentication of the target Authentication Trust Level (ATL). The target ATL is specified by the service. The target user ID can be specified by the service (system service or basic system application) or obtained from the system context (third-party application).
Directory Structure
//base/useriam/user_auth_framework
├── frameworks # Framework code
├── interfaces # Directory for storing external interfaces
│ └── innerkits # Header files exposed to the internal subsystems
├── sa_profile # Profile of the Service ability
├── services # Implementation of the Service ability
├── test # Directory for storing test code
├── utils # Directory for storing utility code
├── bundle.json # Component description file
└── userauth.gni # Build configuration
Usage
Available APIs
Table 1 APIs for unified user authentication
| API | Description |
|---|---|
| getAvailableStatus(authType : AuthType, authTrustLevel : AuthTrustLevel) : number; | Obtains the available authentication status. |
| auth(challenge: BigInt, authType : AuthType, authTrustLevel: AuthTrustLevel, callback: IUserAuthCallback): BigInt; | Performs user authentication. |
Usage Guidelines
- Vendors must implement the following in a Trusted Execution Environment (TEE):
- Authentication scheme: Determine the user authentication scheme based on the user credentials entered and the target ATL.
- Authentication result evaluation: Evaluate whether the authentication reaches the target ATL based on the authentication result returned by the executor.
- The APIs defined in the header file
user_auth/v1_0/IUserAuthInterface.idlin the drivers_interface repository must be implemented in a TEE, and the security of user authentication scheme and result evaluation must be ensured.