...
SAK-367 - CharonPortal Tracking of assumed Id's with 'Return to...'
part two of two
2) CharonPortal patch: - assumed identities tracked with 'Return to <Eid>' link next to Logout link
create special url ('/realuser') that the portal will use to reload any existing previous usage session
Test for sub-story SAK-354: add realm based security to SuTool
This test plan covers the sub-story SAK-354: add realm based security to SuTool ONLY
...
| Panel | ||
|---|---|---|
| ||
Priv User = users that are added to a role in the 'SU Realm' which has the 'Can SU' security function
|
What is expected:
test | source | function | target | result | Test # |
|---|---|---|---|---|---|
SuperUser | can SU | SuperUser | false |
| test 3 |
SuperUser | can SU | Priv User | true |
|
|
SuperUser | can SU | Standard User | true |
|
|
Standard User | can SU | SuperUser | false |
| test 5 |
Standard User | can SU | Priv User | false |
|
|
Standard User | can SU | Stardard User | false |
| test 4 |
Priv User | can SU | SuperUser | false |
| test 6a |
Priv User | can SU | Standard User | true |
| test 6b |
Priv User | can SU | Priv User | true |
|
|
Preparation
- a test site with SU Tool installed (see #SU Tool Setup to set up a course)
- at least two non SuperUser accounts in the test site
- at least two SuperUser accounts
...
| Note | ||
|---|---|---|
| ||
Default realm name and default security function name in tool reg file |
Test 1 - Validate that SU Tool can be created upon access by SuperUser
Login as admin, access the Realms tool, and delete the the realm entitled '!su.can_su_realm'.
Select the tool page (e.g., Administration Workspace) test site that contains the SU Tool.
Type the name of any non-admin or admin user and select 'Become User' button (the later latter case will fail the su, but should achieve the desired results for this test.)
If necessary, log out and re-log in login as an admin user.
Return to Realms tool and search for the above realm name.
Expected result: '!su.can_su_realm' will be created if missing the first time the tool is opened by a SuperUser.
Test 2 - Validate that SU Tool can be created upon access by Standard User
Login as admin and , access the realms Realms tool, and delete the realm entitled '!su.can_su_realm'.
log Log out and re-login as a non-admin user in the test site that has with the SU Tool installed
Select the tool page that contains the SU Tool
log out and relogin as admin.
Log out and re-login as admin.
Return to realms Realms tool and search for the above realm name.
Expected result: '!su.can_su_realm' will be created if missing the first time the tool is opened by and a Standard User.
Test 3
Login as admin and select the tool page that contains the SU Tool
type in the name of another SuperAccount and select 'become user'
...