USER ADMINISTRATION MANAGEMENT DATABASE

1
USER ADMINISTRATION MANAGEMENT DATABASE

• Jussi-Pekka Pispa
• Director, Information Technology

2
Forming a user administration management database

• Personnel data from the personnel management
  system
• Student data from the student register
• Other users data to be included in personnel
  management system
• Data from different source systems must be
  combined and overlapping prevented
• Maintenance of user data from the source systems
  beginning and ending of user rights, changes to
  data

3
Forming user accounts

• User accounts in standard format
• E-mail address firstname.lastname_at_tut.fi
• If more than one e-mail server, mail dropping on
  a server is set by the user
• User profiles must be formed based on user rights
  
• User account database in the form of an LDAP
  directory
• Closing and removal of accounts is automated, an
  advance notification via e-mail

4
Utilizing user data

• Relaying user data to other systems such as
  access control and switchboard
• Standard formats for the transfer of account
  data, such as LDIF (LDAP), compatibility with
  e.g. W2K active directories
• Centralized logging-in to different systems
  through LDAP directory set as objective

5
Volume of work

• Basic work
• Requires cooperation between different parties
• Requires that operational processes are in order
• Basic data must be standardized between different
  systems, e.g. codes for institutes and areas of
  responsibility
• Foreigners social security numbers must be in
  standardized format
• Technically challenging
• Large volume of work

6
Prerequisite for smart card

• The maintenance of user accounts must be in order
  before smart cards can be taken into use
• All users must be entered into the system
• Information security provided by a smart card is
  wasted if user data is not in order