This topic provides guidance on managing user accounts on the Apsara DevOps platform. It covers setting logon session validity, maintaining consistent commit information, standardizing organization usernames, handling administrator changes, and managing member permissions. This information helps you understand and resolve common user account issues.
Set Apsara DevOps logon session validity
Apsara DevOps provides flexible options for setting logon session validity to ensure account security and accommodate different user needs. The default validity is 3 hours, and the maximum validity is 72 hours. Setting an appropriate validity period helps protect your account from unauthorized access and ensures that you can remain online when needed.
Default validity: 3 hours
Maximum validity: 72 hours
Method: For more information, see Set logon duration.
Resolve inconsistencies between the commit user and the Apsara DevOps account name
Git lets you customize user.email and user.name. This can cause the name in a commit record to differ from the actual user, which affects the accuracy of code contribution statistics. Codeup identifies the committer by matching the email address in the commit based on specific rules. You can enable push rule checks to improve security.
Solution:
Exact match principle: Codeup compares the email address in the commit information with the primary email address attached on the server-side (case-sensitive) to ensure correct commit attribution.
Enable code ownership check: After you enable this feature, if the email address in the commit information does not match the server-side email address, the commit is rejected. This prevents spoofing.
Use GPG signing to prevent commit spoofing: GPG signing validates commit records and ensures a trusted source. For more information, see Use GPG signing to prevent commit spoofing.
For the specific procedure, see Why is the displayed commit user different from the Apsara DevOps account name?
Standardize organization username display
Codeup provides organization member names to create a unified and easily recognizable user identity. The organization administrator sets these names to ensure that all internal communications and code repositories use a standardized, reviewed name. For more information, see What is an organization member name?
Handle administrator departure or reassignment
Scenario: A code repository or group may be without an administrator if the current administrator leaves the company or changes position. If this happens, a new administrator must be appointed immediately to maintain normal management and operations.
Procedure:
Find the organization owner: Go to the management console and view the list of organization owners.
Confirm the application administrator: If the current user is an application administrator, the Global Settings entry is visible on the Codeup home page. Click the entry to go to the administrator settings page.
Add a new administrator: As an application administrator, you can add a new administrator with the required permissions to a code group or repository.
For the specific procedure, see What to do if there is no administrator after a user leaves?
Manage member permissions
If a member leaves or their permissions need to be temporarily disabled, the organization administrator can make adjustments on the Apsara DevOps platform. These adjustments include disabling or removing members.
Procedure:
Disable a member: You can disable the member in the management console. This removes all their group and repository permissions. When you re-enable the member, their permissions are automatically restored.
Remove a member: In the member management interface, you can select the remove option. You must then manually reassign permissions if the member requires access again.
Update merge request assignments: If a member assigned to a merge request no longer has the required review permissions, the initiator or an administrator must promptly reassign the request to another member.
For more information, see How are permissions revoked after a member is disabled or removed in the Organization Management console?
Summary
This topic covers several aspects of user account management, including basic logon session management, advanced user information standards, and permission adjustments for personnel changes. This guidance helps you effectively manage and optimize user account settings on the Apsara DevOps platform. If you have other questions or need more help, contact us.