Upstream/harbor
1
0
Fork 0
mirror of https://github.com/goharbor/harbor.git synced 2024-11-30 06:03:45 +01:00
Code Issues Projects Releases Wiki Activity
4f9b581e1b
harbor/tests/testcases/Group3-RBAC/3-07-LDAP-usergroup-manage-project-groupmembers.md
Josh Soref dfe360040b Spelling 
* addition
* attribute
* auditing
* availability
* available
* bandwidth
* browser
* business
* cadence
* chartmuseum
* client
* column
* content
* demonstrate
* described
* endpoints
* facilitate
* github
* harbor
* information
* instance
* manual
* meaningful
* operation
* overridden
* password
* possible
* project
* refactor
* replication
* requires
* running
* scanned
* settings
* signup
* those
* unsigned
* vulnerability

--
Also removes trailing space from a filename

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
2021-02-19 11:59:15 +08:00

2.7 KiB
Raw Blame History

Test 3-07 - LDAP usergroup manage project group members

Purpose:

To verify LDAP group can be assigned a role in project member

References:

User guide

Environment:

  • This test requires that a Harbor instance is running and available.
  • An LDAP server is running and available, and enabled memberof overlay feature
  • 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.
  • LDAP group config parameter are configured.
    1. ldap_group_basedn
    2. ldap_group_filter
    3. ldap_gid
    4. ldap_group_scope
  • A linux host with Docker CLI installed (Docker client).

Test Steps:

  1. Create group harbor_guest, harbor_dev, harbor_admin in LDAP.

  2. Create LDAP user guest_user, dev_user, admin_user in LDAP. Assign add group following members

    • harbor_guest --- guest_user, admin_user.
    • harbor_dev --- dev_user.
    • harbor_admin --- admin_user.

  3. Login as admin user, create private project proj_group_test

  4. Add following group with the roles to proj_group_test

    • harbor_guest --- guest, add this member with LDAP Group DN directly: cn=harbor_guest,ou=groups,dc=example,dc=com.
    • harbor_dev --- developer, create user group with LDAP group DN directly: cn=harbor_developer,ou=groups,dc=example,dc=com
    • Add a user group: group DN: cn=harbor_admin,ou=groups,dc=example,dc=com, with name harbor_admin,
    • Add project member, select existing user group harbor_admin, assign role administrator.

  5. Login user guest_user, dev_user, admin_user in web console. all of them can see the proj_group_test.

    Expected Results:

    • All LDAP users guest_user, dev_user, admin_user can login and see the proj_group_test in web console.
    • guest_user has guest role in proj_group_test
    • dev_user has developer role in proj_group_test
    • admin_user has administrator role in proj_group_test

  6. Login user guest_user, dev_user, admin_user in command line. try to push pull images.

    Expected Results:

    • All LDAP users can login to harbor in command line.
    • guest_user -- can pull images
    • dev_user -- can pull/push images
    • admin_user -- can pull/push images

  7. Remove admin_user from LDAP group harbor_admin, login again with admin_user. check the role in project proj_group_test

    Expected Results:

    • After remove harbor_admin membership, the admin_user should have guest role in project proj_group_test.

  8. Remove admin_user from LDAP group harbor_guest, login again with admin_user, check the role in project

    Expected Results:

    • After remove harbor_guest membership, the admin_user can not see the project proj_group_test.