Summary

This document describes the test plan to test the functionality of the LDAP Group Sync to Roles feature for Mattermost v5.20.

...

When images exist in parallel to assist with the test case, they are placed right below the corresponding test cases.

Scope

This document outlines the tests for LDAP Group Sync to Roles - UI and Functionality features including system console and chat facing changes.

Glossary

• Main menu

  • Hamburger menu on the LHS.

• Channel menu

  • Dropdown menu which is displayed when we click on the Channel Name

• Team Admin

  • A user who has a team administrator privileges of a team but with non-system administrator privileges.

• Channel Admin

  • A user who has a channel administrator privileges of a channel but with non-system administrator (or) non-team admin privileges.

• LDAP Group Sync Job

  • This is an option provided in the System Console > AD/LDAP page.

• Test Server

  • A list of test server versions used in testing including Mattermost server and Marketplace Server

Assumptions

The tests in this test plans are written with the assumption that:

1. Testing done on System Console pages is done as a System Administrator, unless otherwise specified by the test case.

2. Testing is primarily done on the webapp and desktop app, with spot checks on RN mobile app or mobile web browser app to ensure the feature is not present.

Setup

1. The following setup will be necessary in order to begin testing:

...

• Go to the main menu

• Go to “About Mattermost”

• Mattermost version appears on the About modal

Test Cases

System Console > Manage Teams

System Console > Team Configuration - UI

...

System Console > Manage Channels

System Console > Channel Configuration - UI

...

System Console > Manage Groups

System Console > Group Configuration - UI

...

Chat Facing > Teams > Manage Groups

Promote Group Role to Team Admins

...

Chat Facing > Channels > Manage Groups

Promote Group Role to Channel Admins

...

Mapping to Server Scoped Role - System Admin Filter

LDAP Admin Filter

1. Ensure LDAP setup is done correctly on an instance

2. Navigate to System Console > AD/LDAP and set Admin Filter to "(givenName=barrett)" and set Enable Admin Attribute to true.

3. Login as a LDAP user who has this attribute "givenName=barrett" configured in the AD/LDAP Server.

4. Check if the user is logged in as System Admin User and has access to System Console

   1. User should be logged in as System Admin User. User should be able to access System Console without any errors

Disable LDAP Admin Filter

1. Ensure LDAP setup is done correctly on an instance

2. Navigate to System Console > AD/LDAP and set Admin Filter to "(givenName=barrett)"

3. Login as a LDAP user who has this attribute "(givenName=barrett)" configured in the AD/LDAP Server

4. Now login as sysadmin and set Enable Admin Attribute to false and check

   1. Existing LDAP System Admin users should not be demoted to members. Any new LDAP user who tries to login with "givenName=barrett" will no longer be considered a System Admin user and instead should be considered a regular member

Change LDAP Admin Filter

1. Ensure LDAP setup is done correctly on an instance

2. Navigate to System Console > AD/LDAP and set Admin Attribute to "(givenName=test)"

3. Now on a new browser login with a user who has "(givenName=barrett)". User would be logged in as Member.

4. Navigate to System Console > AD/LDAP and set Admin Attribute to "(givenName=barrett)"

5. Revoke session of all users and ensure the user in step 3 logs in again.

6. Next time the user logs in, the user should be converted to a System Admin user.

LDAP Admin Filter & Guest Attribute

1. Ensure LDAP setup is done correctly on an instance

2. Ensure Guest Access is enabled in System Console > Guest Access.

3. Navigate to System Console > AD/LDAP and set Admin Filter to "(givenName=barrett)" and set Guest Attribute to "(sn=Butler)" .

4. Now on a new browser login with a user who has both sn=Butler and givenName=barrett.

   1. User should be logged in as a System Guest user and should not have System Admin privileges.

SAML Admin Attribute

1. Ensure SAML setup is done correctly on an instance

2. Navigate to System Console > SAML 2.0 and set Admin Attribute to "isAdmin=true" and set Enable Admin Attribute to true.

3. Login as a SAML user who has this attribute "isAdmin=true" configured in the SAML Server.

4. Check if the user is logged in as System Admin User and has access to System Console

   1. User should be logged in as System Admin User. User should be able to access System Console without any errors

Disable SAML Admin Attribute

1. Ensure SAML setup is done correctly on an instance

2. Navigate to System Console > SAML 2.0 and set Admin Attribute to "isAdmin=true"

3. Login as a SAML user who has this attribute "isAdmin=true" configured in the SAML Server

4. Now login as sysadmin and set Enable Admin Attribute to false and check

   1. Existing SAML System Admin users should not be demoted to members. Any new SAML user who tries to login with isAdmin=true will no longer be considered a System Admin user and instead should be considered a regular member

Change SAML Admin Attribute

1. Ensure SAML setup is done correctly on an instance

2. Navigate to System Console > SAML and set Admin Attribute to "isAdmin=TEST".

3. Now on a new browser login with a user who has isAdmin=true. User would be logged in as Member.

4. Navigate to System Console > SAML and set Admin Attribute to "isAdmin=TRUE".

5. Revoke session of all users and ensure the user in step 3 logs in again.

6. Next time the user logs in, the user should be converted to a System Admin user.

SAML Admin Attribute & Guest Attribute

1. Ensure SAML setup is done correctly on an instance

2. Ensure Guest Access is enabled in System Console > Guest Access.

3. Navigate to System Console > SAML and set Admin Attribute to "isAdmin=TRUE" and set Guest Attribute to "isGuest=TRUE".

4. Now on a new browser login with a user who has both isGuest=true and isAdmin=true.

   1. User should be logged in as a System Guest user and should not have System Admin previliges.