Feature Wiki
Tabs
Use IP-Range as Object Precondition
Page Overview
[Hide]- 1 Initial Problem
- 2 Conceptual Summary
- 3 User Interface Modifications
- 4 Additional Information
- 4.1 Involved Authorities
- 4.2 Technical Aspects
- 4.3 Privacy
- 4.4 Security
- 4.5 Contact
- 4.6 Funding
- 5 Discussion
- 6 Implementation
- 6.1 Description and Screenshots
- 6.2 Test Cases
- 6.3 Privacy
- 6.4 Approval
If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.
1 Initial Problem
Starting from ILIAS 10, Tests can be restricted by IP address ranges (instead of the previous binding to a single IPv4 address). While this is particularly useful for tests being held in e.g. computing pools of schools and universities, we feel that this is could be extended to e.g. entire courses that shall only be completed on computers whose network address is in a particular range (and, by extension, computing pools). Leveraging course preconditions for this even allows to make different objects accessible to learners in different rooms by putting them in separate courses (and configuring the courses to be hidden if their preconditions are not met).
2 Conceptual Summary
We feel that this could be implemented by extending the functionality of Test: Add IP Ranges as Access Constraint to Test Settings in order to make it a supported Precondition.
Integration of Preconditions in Settings Tab
3 User Interface Modifications
3.1 List of Affected Views
- New View containing the same input options as ParticipantTableIpRangeAction.getModal()
- Further discussion with the A11y/UX/UI Expert Group is necessary in order to determine proper integration into the existing precondition workflow.
3.2 User Interface Details

3.3 New User Interface Concepts
None.
3.4 Accessibility Implications
None.
4 Additional Information
4.1 Involved Authorities
- Authority to Sign off on Conceptual Changes: {Please add related profile link of this person}
- Authority to Sign off Code Changes: {Please add related profile link of this person}
If this request is related to multiple components, please list both authorities for all related components.
4.2 Technical Aspects
This depends on the same
4.3 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.
4.4 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.
4.5 Contact
Author of this request: Meißner, Bastian [simple_oaktree]
This request was created in association with Roeser, Nico [nicoroeser].
4.6 Funding
Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.
If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.
The University of Regensburg is planning to implement this.
5 Discussion
6 Implementation
Feature has been implemented by {Please add related profile link of this person}
6.1 Description and Screenshots
{ Description of the final implementation and screenshots if possible. }
6.2 Test Cases
Test cases completed at {date} by {user}
- {Test case number linked to Testrail} : {test case title}
6.3 Privacy
Information in privacy.md of component: updated at {date} by {user} | no change required
6.4 Approval
Approved at {date} by {user}.
Last edited: 21. Jan 2026, 12:49, Meißner, Bastian [simple_oaktree]