Version 1 (modified by pjkersha, 15 years ago) (diff)


Role Mapping

Role mapping enables data providers to share data with other trusted providers (or trusted host). Sharing is by means of bilateral agreement between data provider and trusted host. Each publish a list of user authorisation roles which they wish to make available. These roles can correspond to data sets, projects or organisational groups that the provider holds. They could also relate to a role a person has indicating what rights they have to access data e.g. PhDStudent or bodcStaff.

To map roles, the data provider makes a map configuration file containing the names of trusted hosts. For each host there is a list of role mappings i.e. for each of the data provider's local roles specified a role from the trusted host is also given. When a user from the trusted host attempts to access data from the data provider, one of their roles can be mapped to a role of the data provider using the role mapping. For the mapping to work, the user must have a role which maps to the required data provider role.

Role mapping matrix

This table shows the current status for NDG role mappings:

Mapping to BADCMapping to BODCMapping to NOCSMapping to PML
BADC N/A X (05/10/05)
BODC X (05/10/05) N/A
NOCS X (06/03/06) N/A
PML X (21/02/06) X (21/02/06) N/A


  • The diagonal is set with N/A because it doesn't make sense for a data provider to map to themselves.
  • An 'X' denotes where mappings have been made.
  • Date next to the X in () shows when the mapping was last updated.
  • A blank cell indicates no mapping is present.