Test: Add IP Ranges as Access Constraint to Test Settings

1 Initial Problem

Currently, it is only possible to add single IP (IPv4) addresses to participants to limit the access to a test. Or work with a *-Placeholder. It is not possible to define a range of IP addresses for a whole test.

But, e.g. in PC-Pools and many participants, it is not possible to always control, on which PC a participant sits and therefor which IP-Address the participant will have when the test begins.

To achieve better control over the test access, we want to add the option to define an IP-Range per test.

2 Conceptual Summary

We want to add this option to the section Administering the Test: Access, right before "Select Participants Manually".

1. It will only be possible to define an IPv4 OR an IPv6 Range.
2. The Range will be defined with a minimal IP and maximal IP field.
3. All IP-addresses (including the addresses in the fields) within this range will be allowed to start the test.
4. Other people, who open this test, will be noticed with the byline "Your IP address is not in the allowed IP range to access this test." below the test title.
5. Also, the Launcher-Button is deactivated and shows the message: "Your IP address is not in the allowed IP range to access this test.".

3 User Interface Modifications

3.1 List of Affected Views

• lObjTestSettingsMainGUI

3.2 User Interface Details

Mockups

3.3 New User Interface Concepts

No new user interface concepts

3.4 Accessibility Implications

No implications from our point of view.

4 Technical Information

{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

5 Privacy

ILIAS checks the IP of a user, if the IP is inside or outside the defined range. But this is not a new date.

6 Security

This feature does not have negative security implications. Some could think this makes the access to a specific test, where the setting is activated, safer.

7 Contact

• Author of the Request: Strassner, Denis [dstrassner], Kergomard, Stephan [skergomard]
• Maintainer: Strassner, Denis [dstrassner]
• Implementation of the feature is done by: Strassner, Denis [dstrassner], Kergomard, Stephan [skergomard]

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• KIT

9 Discussion

Kunkel, Matthias [mkunkel], 17 JAN 2024: Chap. 2, point 4 mentions a ‘byline‘ to notify users about their wrong IP address. IMHO it should be an Info Message Box straight under the tabs. This is the usual place to notify users about obstacles in the workflow. Presenting the message also on the Launcher is fine for me.

JourFixe, ILIAS [jourfixe], 22 JAN 2024: Suggestion is highly appreciated and feature scheduled for ILIAS 10. We keep the message in the byline (where it is already), mainly because it is already visible in the upper container (as known from 'offline' status)

10 Implementation

{ The maintainer has to give a description of the final implementation and add screenshots if possible. }

Test Cases

Test cases completed at {date} by {user}

• Testcases will be added as soon as Testing for ILIAS 9 is done.
• {Test case number linked to Testrail} : {test case title}

Privacy

Information in privacy.md of component: updated on {date} by {user} | no change required

Approval

Approved at 08.03.2024 by Wandelmaier, Franziska [iv5526].