WP1 LB RGMA authorization requirements
======================================

The data
--------

- one table - JobState, each row represents one job state change event,
  - there is a column with job owner DN,

- produced by Bookkeeping server for actual VO.


Authorization requirements
--------------------------

- Basic - user can read data about their own jobs only
  - implicit rule based only on data (owner DN) and user authentication
    identity.

- Advanced (general)
  - general ACLs for job status data access by authorized identities,
  - based on VOMS groups and roles,
  - to be defined by VO administrator.


General requirements
--------------------

- Security - some published data can be confidential (like the actual JDL
  used and available in some of the events stored in the bookkeeping server)

- LB info will flow through intermediate RGMA components (archivers), not only
  single consumer-producer. This implies security and integrity constraints
  (intermediate nodes must not loose data nor they can provide data to
  untrasted parties)

- The advanced rules (ACLs) to be implemented by "EDG standard way" (connected
  to VOMS etc.), LB service is not the service where to define such rules. The
  idea is to publish to RGMA and let the infrastructure (RGMA, VOMS, etc.) to
  react on user requests and provide access rules (authorization) enforcement.


                                                          Jiri Sitera