Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Associating properties to entities (be they persons, identities in general, or themselves groups or roles) may be done in a variety of different ways. Similarly, the conveyance of these properties, and their binding to entities, varies depending on the architectural model of the authentication and authorization system. Yet regardless of the model chosen, trust placed in the attributes relies on the operational security integrity of the authority that manages them.

We are developing guidance that will The guidance is intended to help attribute authorities but also operators of other proxy elements in the BPA model that manage sentitive sensitive credential data with appropriate management and operational security praticespractices.

Some elements are (partially) dependent on the architectural model chosen for the authoritative attribute source. This document therefore distinguishes technology profiles for attribute authorities: (i) attribute authorities that permit binding of properties to entities by means of lookup in which the entity whose properties are sought is the key in the look-up (‘pull model’) and (ii) attribute authorities that issue (usually integrity-protected and, optionally, confidentiality-protected) statements in which attributes are asserted (‘push model’)


Preperatory working materials

Revision 2 - commentable version for review by the (AEGIS) Infrastructures

Guideline 48 revision 2 (initiated February 2020) will evolve and clarify the scope of the guidance for Attribute Authority operators. Comments and suggestions to revision 2 are invited by email to the AARC Community policy list and as comments to the collaborative document here:

Supporting material: