Go to file
openharmony_ci e912957a43
!290 del: 删除人脸ux 相关代码 相关功能转移到 face_auth模块
Merge pull request !290 from shipengtao9579/delface
2022-07-04 11:09:49 +00:00
common Add hitrace and hidumper 2022-07-03 20:34:19 +08:00
dfx Add hitrace and hidumper 2022-07-03 20:34:19 +08:00
figures 架构调整后readme信息修改 2022-05-17 14:46:14 +08:00
frameworks !290 del: 删除人脸ux 相关代码 相关功能转移到 face_auth模块 2022-07-04 11:09:49 +00:00
interfaces !293 PIN离线防暴力破解相关接口上库 2022-06-30 09:54:09 +00:00
sa_profile useriam部件化整改:部件名修改,目录修改 2022-06-15 13:29:48 +08:00
services Add hitrace and hidumper 2022-07-03 20:34:19 +08:00
test UT fail fix 2022-07-04 14:55:49 +08:00
.gitignore add userauth executor 2022-05-08 22:46:36 +08:00
bundle.json adjust new service folders and deleled unused files 2022-06-27 17:37:36 +08:00
LICENSE fix UserAuth issue 2022-03-12 20:47:37 +08:00
OAT.xml fix issue 2022-03-24 19:04:27 +08:00
README_ZH.md README.md README_ZH.md 更新仓名 2022-06-22 12:00:55 +08:00
README.md README.md README_ZH.md 更新仓名 2022-06-22 12:00:55 +08:00

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

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):
  1. Authentication scheme: Determine the user authentication scheme based on the user credentials entered and the target ATL.
  2. 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.idl in the drivers_interface repository must be implemented in a TEE, and the security of user authentication scheme and result evaluation must be ensured.

Repositories Involved

useriam_user_auth_framework

useriam_pin_auth

useriam_face_auth

drivers_peripheral

drivers_interface