On this page

Show all

Help Center/ CodeArts Repo/ Service Overview/ Security/ Authentication and Access Control

Authentication and Access Control

Updated on 2025-01-22 GMT+08:00

View PDF

Authentication

Regardless of whether you access CodeArts Repo through the management console or APIs, CodeArts Repo uses Identity and Access Management (IAM) for authentication.

CodeArts Repo supports two authentication modes:

Token authentication: Requests are authenticated using a token.
AK and SK authentication: Requests are encrypted using an Access Key ID (AK) / Secret Access Key (SK). This method is recommended because it provides higher security than token-based authentication.

For more authentication details, see Authentication.

Access Control

IAM permission management
Permission management is a fine-grained authorization based on roles and permissions. Different operation permissions are assigned to different roles based on their work requirements. Users can access only authorized resources.

Roles in CodeArts Repo include the product manager, test manager, O&M manager, system engineer, committer, developer, tester, participant, viewer, and custom role.
IP address whitelist control
- IP address whitelists enhance repository security by restricting access to repositories by IP address.
- You can access repositories only from whitelisted IP addresses. Access requests from other IP addresses are rejected.
- IP address whitelists include tenant-level IP address whitelists and repository-level IP address whitelists, and their priorities can be configured.
For details about how to configure the IP address whitelist, see IP Address Whitelist.
Repository Locking
When a new software version is ready for release, administrators can lock the repository to protect it from being compromised. After the repository is locked, no one (including the administrators) can commit code to any of its branches.

For details about how to lock a repository, see Repository Locking.
Protected Branch Management
Protected branches prevent pushes to the branches and prevent the branches from being incorrectly deleted.
- Secure branches and allow developers to use merge requests to merge code.
- Prevent non-administrators from pushing code.
- Prevent all forcibly push to this branch.
- Prevent anyone from deleting this branch.
For details about how to configure branch protection, see Protected Branches.
O&M SOD
The purpose is to standardize O&M scripts throughout the development, test, and release process (including script development, code review, manual test, integration acceptance, release review, script rollout, and version management). Promote and strengthen standardized operation management to ensure process, security, and quality compliance.
Isolation Between Firewalls and VPCs
CodeArts Repo uses firewalls and VPCs to isolate networks and resources between tenants.

Parent topic: Security

Previous topic: Shared Responsibilities

Next topic: Data Protection Technologies

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot