GRIDipedia – The European Grid Marketplace

The aim of this pattern is to solve the problems linked to managing identity material. Indeed, the identity of an entity can evolve during time (it can be revoked, changed …)

In some situations, an identity of an entity can evolve by example it can be revoked. Sometimes some data encrypted by this entity must be decrypted. In this situation, a key manager is useful to retrieve old identity in order to decrypt the data.

This pattern is useful when keys can evolve during time and old data must be retrieved. It’s also useful to manage entities identity.

The KeyManager is used to maintain an historic of identities and to be a single point to manage identity materials.
The SecurityEvent is a piece of data containing informations about a security change.
An HistoricEntry is an element that keep trice of the validy of an entity identity.
Collaboration diagrams are not relevant in this case. Indeed operations are directly invoked on the KeyManager. The Event reporting mechanism is described in the SecurityObserver pattern.

© 2007 BEinGRID