openharmony_ci afeb7fdd9e !59 merge fws into master
llt test构建配置修改

Created-by: qq_35037212
Commit-by: fangwusheng
Merged-by: openharmony_ci
Description: ### 一、内容说明(相关的Issue)

https://gitcode.com/openharmony/accesscontrol_accesscontrol_cangjie_wrapper/issues/34


### 二、建议测试周期和提测地址  
  建议测试完成时间:xxxx.xx.xx  
  投产上线时间:xxxx.xx.xx  
  提测地址:CI环境/压测环境  
  测试账号:  无

### 三、变更内容
  * 3.1 关联PR列表
https://gitcode.com/openharmony/accesscontrol_accesscontrol_cangjie_wrapper/pull/59
  * 3.2 数据库和部署说明  
    1. 常规更新 
    2. 重启unicorn
    3. 重启sidekiq
    4. 迁移任务:是否有迁移任务,没有写 "无"
    5. rake脚本:`bundle exec xxx RAILS_ENV = production`;没有写 "无"
无
  * 3.4 其他技术优化内容(做了什么,变更了什么)
   根据仓上对应分支修改用例工程构建配置,Dev/Trunk分支修改为6.1.0-APILevel23,Cangjie-build-support同样匹配对应版本构建方式
	主要修改:
	hvigor-config.json5文件
	test目录下build-profile.json5文件
	检查module.json5中的设备类型HarmonyOS工程为"phone",OpenHarmony工程对应为"default"


  * 3.5 废弃通知(什么字段、方法弃用?)
不涉及


  * 3.6  后向不兼容变更(是否有无法向后兼容的变更?)

不涉及
  
### 四、研发自测点(自测哪些?冒烟用例全部自测?)
  自测测试结论:
 	测试通过

### 五、测试关注点(需要提醒QA重点关注的、可能会忽略的地方)
  检查点:

| 需求名称 | 是否影响xx公共模块 | 是否需要xx功能 | 需求升级是否依赖其他子产品 |
|------|------------|----------|---------------|
| xxx  | 否          | 需要       | 不需要           |
|      |            |          |               |

  接口测试:不涉及

  性能测试:不涉及

  并发测试:不涉及

  其他:



See merge request: openharmony/accesscontrol_accesscontrol_cangjie_wrapper!59
2026-04-07 21:22:58 +08:00
2025-09-26 14:29:40 +08:00
2026-01-27 10:34:20 +08:00
2026-01-06 09:11:36 +08:00
2025-08-23 16:00:15 +08:00
2025-11-22 17:24:40 +08:00
2026-01-07 10:16:17 +08:00
2025-08-23 16:00:15 +08:00
2025-08-23 16:00:15 +08:00
2025-10-07 14:46:54 +08:00
2025-10-07 15:04:30 +08:00

accesscontrol_cangjie_wrapper(beta feature)

Introduction

The accesscontrol_cangjie_wrapper is a Cangjie API encapsulated on OpenHarmony based on the access_token capability. The access_token information of the application mainly includes the application identity APPID, user ID, application clone index, application APL (Ability Privilege Level) level, application permission information, etc. The access_token information of each application is identified by a 32-bit unique device identifier, TokenID. Cangjie apis provides APIs for application permission management, including authentication and authorization. The currently accesscontrol Cangjie api only supports standard devices.

System Architecture

Figure 1 System architecture of accesscontrol_cangjie_wrapper

accesscontrol_cangjie_wrapper architecture

As shown in the architecture diagram:

interface: Provides APIs for developers.

  • abilityAcessCtrl:
    • checkAccessToken: accesscontrol_cangjie_wrapper provides permission verification and management capabilities for applications. Developers can check whether an application has been authorized.
    • requestPermissions: Developers can request user authorization, and the result of this permission application will be returned.

frameworks:

  • abilityAcessCtrl wrapper:
    • checkAccessToken wrapper: Encapsulates the checkAccessToken interface, providing developers with the ability to check whether an application has been authorized.
    • requestPermissions wrapper: Encapsulates the requestPermissionsFromUser interface, providing developers with the ability to request permissions from users.

Dependency Component Introduction in Architecture:

  • access_token: It is responsible for providing basic functions of application access control, and encapsulates C interfaces to provide interoperability for Cangjie.
  • hiviewdfx_cangjie_wrapper: Responsible for providing HiLog APIs, used for printing logs at critical paths.
  • cangjie_ark_interop: Responsible for providing APILevel definitions, used for annotating APIs. Also provides the BusinessException exception class definition that is thrown to users.
  • ability_cangjie_wrapper: Responsible for providing UIAbilityContext to the authorization interface for launching permission request dialogs to users.

Directory Structure

The source code of the program access control is under base/accesscontrol/accesstrol_cangjie_wrapper

base/accesscontrol/accesscontrol_cangjie_wrapper
├── figures                       # architecture pictures
├── ohos                          # Cangjie program access control interface
│   ├── ability_access_ctrl       # Cangjie program access control management interface
│   └── security                  # Permission request result object
└── test                          # Cangjie test code
    └── ability_access_ctrl       # Cangjie AbilityAccessCtrl test code

Usage Guidelines

The following features are provided:

  • The AbilityAccessCtrl module provides APIs for application permission management, including authentication and authorization. For relevant guidance, please refer to Requesting User Authorization.

The following features are not provided yet:

  • Check the status of application permissions.
  • Displays a dialog box for setting a global swich.
  • Displays a permission settings dialog box to grant permissions the second time.

For Accesscontrol-related APIs, please refer to ohos.ability_access_ctrl (Application Access Control Management). For relevant guidance, please refer to Access Control Overview.

Code Contribution

Developers are welcome to contribute code, documentation, etc. For specific contribution processes and methods, please refer to Code Contribution.

Constraints

The following features are not provided yet:

  • Check the status of application permissions.
  • Displays a dialog box for setting a global swich.
  • Displays a permission settings dialog box to grant permissions the second time.

Repositories Involved

security_access_token

arkcompiler_cangjie_ark_interop

ability_ability_cangjie_wrapper

hiviewdfx_hiviewdfx_cangjie_wrapper

S
Description
仓颉程序访问控制能力封装层
Readme 2.7 MiB
Languages
Cangjie 97.4%
Python 1.4%
TypeScript 1.2%