Date: August 31, 2012
Author: Oscar Koeroo

README for the LCMAPS Jobrepository plug-in
===========================================

The LCMAPS Jobrepository plug-in stores credentials and the resulting account
mappings into a relational database. This plugin will link up all the known
in-process information from LCMAPS core memory and stores it in a database. This
plug-in uses ODBC (http://en.wikipedia.org/wiki/ODBC) to connect to the
database.

The current state of the mappings between various credentials and Unix accounts
is stored in an open database on disk, but this information can change over
time through (regular) system administrative interventions. This state is now
preserved in a relational database with the added benefit of being accessible
by other systems, e.g. GridSAFE and build-up an easy to backup historic view on
the mapping state.

Quite some systems seem to dig up data by trawling log files, e.g. to construct
accounting data records. This method is subjected to the settings of the
sub-systems which control the format of the log file output. Log trawling tools
are interacting with the log files as a glorified API. This lowers the ability
for tools, e.g. LCMAPS, to alter their log output. By offering the LCMAPS
Jobrepository plug-in as an alternative with the added benefit of offering
the data in a structured fine-grained database with the ability of an
historic view the intend is to avoid the need and/or requirement for log
file trawling.

.SH DATABASE SCHEMA EXTENSIONS
The schema can be used to link up account mapping and/or credential mapping
results originating from other credential types and link up more fine grained
details from the specific work environment, i.e. a Gatekeeper and GridFTPd will
be able to add service specific information together with the mapping results.
