Nowadays, computer labs in academic institutions employ two major methods of
user sign-in. These are "Counter sign-in", when Lab Assistants assign incoming users
to workstations, and "Self-Service sign-in", when users log in using account
credentials stored in an enterprise directory such as LDAP or MS Active Directory.
Both methods exist in a variety of flavors. Here we will explain how VeraLab supports
these scenarios, and how VeraLab adds value in each scenario.
Counter Sign-In
Every incoming user signs in to a workstation through a Lab Assistant who is
responsible for assigning users to computers in a computer room. The Lab Assistant
verifies the users identification. The degree of automation may vary.
Some institutions maintain a paper log where students are recorded. Others
deploy a sign-in application that keeps access logs in a digital form.
Those who are most computer savvy deploy a Lab Management System with
advanced security, access control, and surveillance capabilities.
Self-Service Sign-In
Every user has an account created in a central directory. Registered users who
come to a lab are free to choose any available workstation and log
in using their account credentials. Lab personnel provide technical
or customer support rather than access control.
How VeraLab Supports a Self-Service Scenario
Each workstation in the lab is equipped with VeraLab Guard, the module that performs the
monitoring the workstation log-in state.
Once a user logs in (presumably using directory authentication), VeraLab Guard sends
a log-in notification to VeraLab Server. VeraLab Server validates the user against
Alert List and checks whether the workstation is available for user sign-in.
In case the Alert List prohibits the user from signing-in or the workstation has
been marked as unavailable for sign-in, VeraLab Server responds to VeraLab
Guard with logout response. As a result VeraLab Guard logs the user out.
Once the user logs out, VeraLab Guard sends a
logout notification to the VeraLab Server, and the VeraLab
Server records the end of the user session.
Lab Assistants can occasionally view the status of the lab through the "Monitor" module.
This module will show them the current status for each workstation including user names of
signed-in users, Alert List notifications, workstation occupancy, and availability.
Figure 1. Screenshot of Monitor module
How VeraLab Supports the Counter Sign-in Scenario
VeraLab provides Lab Assistants with a "Dashboard" module that supports the following front-end activities:
- Assigning users to workstations. Data from the user ID card are scanned and saved to the access log database. Users can be assigned to and unassigned from workstations. Unattended workstations can be locked to prevent unauthorized access. Locking/unlocking can be integrated with user sign-in.
- Viewing computer room status. The Lab Assistant can view the occupancy of multiple computer rooms and can redirect incoming users from over-occupied to under-occupied rooms.
- Alert List notifications. To prevent abusers from accessing a computer facility, the Lab Assistant will be notified if the incoming user has been added to the Alert List.
- Class registration. To prevent public access while a class is being performed, the Lab Assistant can mark the room as occupied for the class.
Figure 2. Screenshot of Lab Assistant Dashboard
