Skip to main content

Authorization markup languages

 Authorization Markup Languages are XML-based languages that are used to define access control policies and rules for authorization purposes. These languages provide a structured way to specify who has access to what resources and under what conditions. Here are a few commonly used authorization markup languages:


XACML (eXtensible Access Control Markup Language):

XACML is a widely adopted standard for access control policies and authorization management. It provides a flexible and expressive framework for defining fine-grained access control rules. XACML allows you to specify policies, rules, and conditions based on various attributes, subjects, resources, and actions.


SAML (Security Assertion Markup Language):

SAML is an XML-based standard for exchanging authentication and authorization information between different parties. While it is primarily used for Single Sign-On (SSO) scenarios, SAML also includes elements for authorization, such as attribute assertions that can be used to convey authorization decisions.


ALFA (Abbreviated Language for Authorization):

ALFA is a high-level, human-readable language used to define access control policies. It is designed to be easily understandable by both technical and non-technical users. ALFA can be used to express authorization policies and is often used in conjunction with the XACML standard.


ODRL (Open Digital Rights Language):

ODRL is an XML-based language for expressing permissions, obligations, and conditions related to the usage of digital content. While its primary focus is on digital rights management, ODRL can also be used to define authorization policies and access control rules.


These authorization markup languages provide standardized ways to specify access control policies and rules, facilitating interoperability and consistency in authorization management across different systems and applications.

Comments

Popular posts from this blog

2.1 VIRTUAL MACHINES PROVISIONING AND MANAGEABILITY

In this section, we will have an overview on the typical life cycle of VM and its major possible states of operation, which make the management and automation of VMs in virtual and cloud environments easier than in traditional computing environments As shown in Figure above, the cycle starts by a request delivered to the IT department, stating the requirement for creating a new server for a particular service.  IT administration to start seeing the servers’ resource pool, matching these resources with the requirements, and starting the provision of the needed virtual machine.  Once provisioned machine started, it is ready to provide the required service according to an SLA, or a time period after which the virtual is being released.

1.2 ROOTS OF CLOUD COMPUTING

We can track the roots of clouds computing by observing the advancement of several technologies, especially in hardware (virtualization, multi-core chips), Internet technologies (Web services, service-oriented architectures, Web 2.0), distributed computing (clusters, grids), and systems management (autonomic computing, data center automation).  Below Figure shows the convergence of technology fields that significantly advanced and contributed to the advent of cloud computing. . We present a closer look at the technologies that form the base of cloud computing, with the aim of providing a clearer picture of the cloud ecosystem as a whole. 1.2.1 From Mainframes to Clouds 1.2.2 SOA, Web Services, Web 2.0, and Mashups 1.2.3 Grid Computing 1.2.4 Utility Computing 1.2.5 Hardware Virtualization 1.2.6 Virtual Appliances and the Open Virtualization Format 1.2.7 Autonomic Computing ______ Cloud computing has its roots in several technologies and developments, including virtualization, gr...

2.1.1 VM Provisioning Process

  Steps to Provision VM. Here, we describe the common and normal steps of provisioning a virtual server: Firstly, you need to select a server from a pool of available servers (physical servers with enough capacity) along with the appropriate OS template you need to provision the virtual machine. Secondly, you need to load the appropriate software (operating system you selected in the previous step, device drivers, middleware, and theneeded applications for the service required). Thirdly, you need to customize and configure the machine (e.g., IP address, Gateway) to configure an associated network and storage resources. Finally, the virtual server is ready to start with its newly loaded software. These are the tasks required or being performed by an IT or a data center’s specialist to provision a particular virtual machine.