Go to file
liuziwei aa499f1418 add annotation for innerapi
Signed-off-by: liuziwei <liuziwei12@huawei.com>
Change-Id: I9a350f6bcc2edcb0813d61f0728c5b6645811f02
2023-03-06 02:18:41 +00:00
common add for user auth executors 2023-03-02 04:45:24 +00:00
figures update readme 2022-07-08 10:36:37 +08:00
frameworks add annotation for innerapi 2023-03-06 02:18:41 +00:00
interfaces/inner_api add annotation for innerapi 2023-03-06 02:18:41 +00:00
param Add framework ready param dac permission 2022-10-24 19:41:27 +08:00
sa_profile add native permission 2022-08-04 20:36:21 +08:00
services Merge https://gitee.com/liuhahahao/useriam_user_auth_framework into 0302lzw 2023-03-02 13:50:31 +00:00
test Merge https://gitee.com/liuhahahao/useriam_user_auth_framework into 0302lzw 2023-03-03 10:32:38 +00:00
.gitignore add userauth executor 2022-05-08 22:46:36 +08:00
bundle.json add for user auth executors 2023-03-02 04:45:24 +00:00
hisysevent.yaml Add space to yaml file parameter format 2023-02-17 09:35:39 +00: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 update readme 2022-07-11 14:22:45 +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