Feature Wiki

Information about planned and released features

Tabs

Session Handling

1 Description

Bundesagentur für Arbeit needs a facility to configure the duration and number of sessions at the same time.
Additionally, the session handling can also be configured across clients.

In the Administration, the session settings can be configured. In order to make this available, across clients, these data can be configured in two different positions:

  • In the ILIAS Setup, the basic configuration of the clients` sessions is selected.
    Additionlly, a setting is needed that determines whether the number of sessions can also be configured in the administration area of a single client.
    • Status "enabled" => Configuration in the administration area is allowed.
    • Status "disabled" => Configuration in the administration area is not allowed! The selected option is visible for the administrator but greyed out.
  • In case the configuration is allowed to ILIAS administrators (s. above), there is also a need for a configuration facility in the administration area.
    These settings are supposed to be available either at the "Basic settings" or in a new dialogue "Sessions".

Configuration of session number
After the maximum number of active sessions has exceeded, users trying to log in additionally are rejected. They receive a message that can be configured by the administrator. As soon as a user logs out actively, or is loged out automatcially after a specific period of inactivity, new users can log in (s. example below).

Configuration of the session duration
For the sake of the highest possible flexibility, to time slots can be defined:
  • The maximum session duration is equivalent to the funtion available in ILIAS currently, i.e., the time slot after which the session of a user is closed after inactivity.
  • Additionally, the facility to onfigure a minimum session duration is planned. Only after this minimum period is exceeded, the system can close the session of an inactive user if new sessions are demanded. In case the maximum number of sessions is not exceeded, the session ends according to the settings of the maimum session duration.
Example settings:
  • Maximum number of sessions: 500
  • Minimum session duration (without activity): 10 minutes
  • Maximum session duration (without activity): 30 minutes

Period of user inactivity

Sessions at a time

ILIAS reaction

5 minutes

250

All of the sessions can take place parallelly. No necessity of new settings.

5 minutes

500

The administrator can configure a personalized status message in a textbox of the "Sessions" dialogue of the administration area that will be display to the user.
Example: „Note: Unfortunately, the maximum number of sessions at a time is exceeded currently, please try again to log in later."

15 minutes

250

All of the sessions can take place parallelly. No necessity of new settings.

15 minutes

500

In case new sessions are started, the session of the users will be closed automatically.
In case the user becomes active again, a status message is displayed. The administrator can configure it in a textbox of the "Sessions" dialogue of the administration area. Example: „Your session was closed due to security reasons! Do you want to re-open the session?" If yes => User gets redirected to the login page.

30 minutes

Session of the user will be closed. The administrator can configure a personalized status message in a textbox of the "Sessions" dialogue of the administration area that will be display to the user.
Example: „Your session was closed due to security reasons! Do you want to re-open the session?" If yes => User gets redirected to the login page.

2 Status

3 Additional Information

  • One issue remained unsolved up to now: Sessions in the Public Area. ILIAS starts a session when the starting page is called, i.e., the session is already active when users view demo contents in the Public Area. The handling of this problem is currently discussed.
  • A related issue is maintaining the session status while a user is working within a SCORM module.
  • If you want to know more about this feature, its implementation or funding, please contact: Norbert Bromberger (bromberger@qualitus.de)

4 Discussion

  • Additional idea (implemented at Bundesagentur für Arbeit): A maximum time of inactivity allowed after having logged in.

JF 29 June 2009: Björn will contact Stefan on this. The whole check will be put into the authentication procedure at a point, where ILIAS "knows" whether it is a normal user / admin / anonymous, to be able to let admins into the system everytime.

5 Follow-up

Last edited: 17. Apr 2025, 15:10, Kunkel, Matthias [mkunkel]