Security Token Service Pattern
Members of a federation must be able to identify one another, identify messages as coming from other members of the federation, and identify the truth of claims made by other parties in the federation. They must also be able to communicate securely.
PDP Pattern
The Policy Decision Point applies policies that control access to resources.
PEP Factory
This pattern could be used when it is desirable to apply on the fly a specific policy, regarding the actions that need to be taken on the incoming/outgoing messages, based on the structure and the characteristics of the message itself.
Event Policy Control
The aim of this pattern is to check and enforce policies on events. A message or event is received and based on that event and the state of data held by the policy manage, certain action is taken. It is possible to update the policy as well as the data on which a decision is made.
End-to-end Security in a Federation Pattern
This is a composite pattern based on the STS, PDP and PEP that is need so that members in a federation can communicate securely and know that they are communicating with members of their federation.
Connection Bridge
The aim of this pattern is to give a way to connect two entities that have firewall blocking input connections. The entities take the initiative of the connection.
Security observer
The aim of this pattern is to ensure that a change in security is reported to each entity of the system that would like to be informed for a category of change.
Encryption level broker
The aim of this pattern is to solve the problem of different level encryption and negotiation between entities about the correct level to choose.
Public Key Manager
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. Etc.)