...
A username is not created if the student does not accept the offer. The username of a student registering as absent remains valid.
1.1.2 A change in a student's identity data
...
How do changes in a student's information propagate from the student registry to the user database?
A student's changed information is updated in the user database in real-time.
1.1.3 A student ceases to be a student
When does the organization (e.g. student administration) consider that a student no longer is a student...
a) after graduation?
b) after the beginning of a new term when the student has not registered as present?
c) after the student reports that she has terminated her studies?
How long does it take after the above mentioned events until the organization (e.g. student administration) close the student's user account or removes the student role?
a) Graduation is recorded in the study register after graduation meeting.
...
c) the termination of studies is recorded in the study register immediately after the matter case has been discussed processed
Logging in to the Haka infrastructure will be prevented immediately after the above recordings.
1.2. The staff registry
...
The personal data registry is the HR system's relational database, and it is linked to the user database via a user interface showing the latest changes which are polled after short scheduled intervals.
1.2.1. A new employee
...
A new employee's data is updated in the user database almost in real-time. A username is created for the user on the basis of the data. If the person already has a username, a new username is not created.
The username is provided to the new employee during orientation.
1.2.2. A change in an employee's identity data
...
Changed data is updated in the user database almost in real-time.
1.2.3. An employee ceases to be an employee
...
An employee ceases to be an employee after she no longer has a current work contract. At the same time also the permission to use the username in that role ends and logging in to the Haka infrastructure is prevented immediately.
1.3. Other users and the freshness of their identity data
...
Are there other users in the organization who have a username and who can log in via the Identity Provider server to the Haka infrastructure services (The Academy of Finland researchers? the restaurant staff? persons undergoing non-military service? Docents? Alumni? Professor emeriti? Library clients?). What kind of application and acceptance procedure do these usernames have? How is the users' user data freshness and closing/updating of role data ensured? Users who are not natural persons (e.g. student organizations) are not end users as meant by the Haka infrastructure and their logging in via the Identity Provider server must not be allowed.
Only Metropolia students and staff can log in to the Haka infrastructure services.
2. Confirming identity
...
2.1 When providing the username
...
How is a new users identity confirmed when she is provided with a username?
A student gets her user information from Helpdesk, Study Affairs Office, or from the tutor at the beginning of studies. The student's identity is confirmed before providing her with the user information.
An employee's get her user information from Helpdesk or her superior. The employee's identity is confirmed at the signing of the work contract and always when the person is not already known.
2.2. When a user logs in using a username
...
Quality requirements of password authentication. Possible other authentication methods stronger than password authentication.
The minimum length of the password is 8 characters.
3. Data available in the user database