UDB: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
Line 30: | Line 30: | ||
* [[User database, authentication and authorisation]] | * [[User database, authentication and authorisation]] | ||
* [[acc]] | |||
[[Category:Pages needing work]] | [[Category:Pages needing work]] |
Revision as of 11:56, 28 August 2023
UDB is an acronym for User Database. It refers to CSE databases whose primary, but not sole, purpose is to supplement staff and student information provided by UNSW to allow the information to be used to manage CSE IT resources.
There are two UDB's:
The New UDB uses PostgreSQL and OpenLDAP (server).
The Old UDB uses custom software developed in-house running over the very deprecated NIS/SunYP. Eventually, it is hoped, this will go away and the only UDB will then be the new UDB.
Making changes to the UDB
The primary method for making changes to the UDB is via the acc
program. This is a command-line utility which can be used to view UDB content or add/modify content in the UDB.
Automated updates to the UDB
- SIMS (see UNSW Systems of Record)
- PIMS (see UNSW Systems of Record)
- CSE host = Synth
What is the UDB used for?
- User logins
- mlalias
- Resource access and allocation (e.g., special-purpose server access, other access privileges, disk quota)
Why supplement?
- CSE lab computers, login servers and VLAB servers require a user name, a password, a numerical user ID (UID), a numerical group ID (GID)) and a home directory location for a user to log in. UNSW's systems only provide the first two of these. The last three must be provided by the UDB for user logins to be possible.