Authentication and Authorisation Infrastructure.
Protection of resources against unauthorized access. Use of resources is regulated according to a security policy and is permitted to authorized system entities only.
Any information used for access control purposes, including contextual information.
Note: Contextual information might include source IP address, encryption strength, the type of operation being requested, time of day, transaction ID, etc. Portions of access control information may be specific to the request itself, some may be associated with the connection via which the request is transmitted, and others (for example, time of day) may be "environmental".
A description of the type of authorized interactions a subject can have with a resource. Examples include read, write, execute, add, modify, and delete.
Collection of the data concerning resource consumption related to the metrics defined in a SLA-contract (see Service-Level-Agreement) established between a Service Customer and a Service Provider. These data are the base for charging the consumer for the services provided to him.
A service that can be used by interacting entities (viz. participants) in order to create a coordination context (see also Coordination).
Owner of agents that either use or provide Web Services. A physical or conceptual entity that can perform actions. Examples: people, companies, machines, running software.
An actor can take on (or implement) one or more roles. An actor at one level of abstraction may be viewed as a role at a lower level of abstraction.
A type of firewall. All internal computers establish a connection with a proxy server. The application gateway examines the packets more thoroughly than a circuit-level gateway when making forwarding decisions. It is considered more secure, but uses more memory and processor resources.
Software engine (computer program that outputs source code or markup code that simultaneously becomes the input to another computer process) that delivers applications to client computers or devices.
A piece of digital information: An artefact may be any size, and may be composed of other artefacts. Examples of artefacts: a message, a URI, an XML document; an image file; a bit stream.
Application Service Provider.
Formally, the administrative domain that hosts one or more SAML authorities. Informally, an instance of an SAML authority.
The process by which principals become associated or affiliated with a trust realm or federation (see also Federation).
An interaction is said to be asynchronous when the associated messages are chronologically and procedurally decoupled. E.g. in a request-response interaction, the client agent can process the response at some indeterminate point in the future when its existence is discovered. Mechanisms implementing this include polling, notification by receipt of another message, etc.
Web service that maintains information (attributes) about principals within a trust realm or federation. The term principal, in this context, can be applied to any system entity, not just a person.
Mechanism used on behalf of an owner that monitors actions and agents to verify the satisfaction of obligations.
The process of verifying that a potential partner in a conversation is capable of representing a person or organization.
The process of determining, by evaluating applicable access control information, whether a subject is allowed to have the specified types of access to a particular resource.
Usually, authorization is in the context of authentication. Once a subject is authenticated, it may be authorized to perform different types of access.
The result of evaluating an applicable policy, returned by the PDP to the PEP. A function that evaluates to Permit, Deny, Indeterminate or NotApplicable", and (optionally) a set of obligations.
Ability of a Service to perform its agreed function when required; usually calculated as a percentage.
© 2007 BEinGRID