OASIS Cloud Authorization (CloudAuthZ) TC

TC Page     Send a comment to this TC

Enabling contextual attributes and entitlements to be delivered to Policy Enforcement Points in real time


The Technical Committee was closed by the OASIS TC Administrator on 08 November 2016 and is no longer active.
Archives of its work remain publicly accessible and are linked from this page. OASIS appreciates the efforts of all those who participated in this TC.

Table of Contents


Participation in the OASIS CloudAuthZ TC is open to all interested parties. Contact join@oasis-open.org for more information.


The CloudAuthZ TC develops enhanced models for managing authorizations and entitlements in SaaS, PaaS, and IaaS contexts. CloudAuthZ enables contextual attributes and contextual entitlements sets to be delivered to Policy Enforcement Points in real time. With CloudAuthZ, authorization decisions can be informed by data such as where users are, what they are doing, which device they are using, etc.

The TC welcomes contributions of relevant use cases for authorization and entitlements. Existing standards (e.g. XACML, OAuth, etc.) will be used wherever possible.

For more information on CloudAuthZ, see the TC Charter.


No subcommittees have been formed for this TC.

TC Liaisons

No TC Liaisons have been announced for this TC.

Technical Work Produced by the Committee

This Committee has not produced technical work yet.

Expository Work Produced by the Committee

There are no approved expository work products for this TC yet.

External Resources

External resources have not yet been identified.

Mailing Lists and Comments

cloudauthz: the list used by TC members to conduct Committee work. TC membership is required to post. TC members are automatically subscribed; the public may view archives.

cloudauthz-comment: a public mail list for providing input to the OASIS CloudAuthZ TC members. Send a comment or view archives.

Press Coverage and Commentary

Additional Information

Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.