Upstream/harbor
1
0
Fork 0
mirror of https://github.com/goharbor/harbor.git synced 2024-07-02 17:55:15 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #5281 from stonezdj/testcase_ldap_group_admin

Browse Source 
Add testcase for define harbor admin by LDAP group DN
This commit is contained in:
stonezdj(Daojun Zhang) 2018-08-07 16:28:49 +08:00 committed by GitHub
commit 1f65f9304f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 31 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
tests/testcases/Group3-RBAC/3-08-LDAP-define-harbor-admin-by-dn.md Normal file
View File

@ -0,0 +1,31 @@
Test 3-08 - Define Harbor Admin By DN (LDAP Mode)
=======
# Purpose:
To verify that harbor admin can be defined by LDAP group DN
# References:
User guide
# Environment:
* This test requires that a Harbor instance is running and available.
* Harbor is set to authenticate against an LDAP or AD server. ( auth_mode is set to **ldap_auth** .) The user data is stored in an LDAP or AD server.
* A linux host with Docker CLI installed (Docker client).
* At least five(5) non-admin users are in Harbor.
# Test Steps:
1. Create group harbor_sys_admin in LDAP.
1. Create LDAP user sys_admin in LDAP, and add sys_admin to the member of group harbor_sys_admin.
1. Login as admin user, Go to Administration -> Configuration -> Authentication, set the configuration: "LDAP Groups With Admin Privilege" with the DN of harbor_sys_admin.
1. Login in with LDAP user sys_admin.
# Expected Outcome:
1. The sys_admin user can have admin privileges, such as change the configuration, add/remove replication policy, manage repositories etc.
# Possible Problems:
None