===== OASIS: eXtensible Access Control Markup Language (XACML) ===== [[dido:public:ra:xapend:xapend.b_stds:tech:oasis:start| return to the OASIS Standards ]] | Title | eXtensible Access Control Markup Language (XACML) | | Acronym | XACML | | Version | 3.0 | | OASIS Document Number | acml-3.0-core-spec-os| | Release Date | 22 January 2013| | About Specification | [[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xacml]] | | Document | [[http://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html]]|
Data sheet for eXtensible Access Control Markup Language (XACML)
: **Note**: The following is an excerpt from the actual document. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. ==== Introduction ==== : //The eXtensible Access Control Markup Language (XACML) [XACML-3] defines an architecture and a language for [[dido:public:ra:xapend:xapend.a_glossary:a:accesscontrol|access control]] ([[dido:public:ra:xapend:xapend.a_glossary:a:authorization| authorization]]). The language consists of requests, responses, and policies. Clients send a request to a [[dido:public:ra:xapend:xapend.a_glossary:s:server|server]] to query whether a given action should be allowed. The server evaluates the request against the available policies and returns a response. The policies implement the organization's access control requirements.[[https://tools.ietf.org/html/rfc7061]]// /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- /* To add a discussion page to this page, comment out the line that says ~~DISCUSSION:off~~ */ ~~DISCUSSION:on|Outstanding Issues~~ ~~DISCUSSION:off~~