OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xacml-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [xacml-comment] 60-day Public Review for REST Profile of XACML 3.0 and JSON Profile of XACML 3.0 COS01 - JSON Profile issues


I take the opportunity of the public review period to report some issues with the JSON Profile. I already reported them in a few months ago (https://lists.oasis-open.org/archives/xacml-comment/201709/msg00000.html ), but I notice they’re still there:


1.       Section 5.2.2 refers to a “PolicyIdentifierList” object whereas 5.2.11 names it “PolicyIdentifier”. Probably a typo.

2.       In 8.1 Request Example,

a.    the Attribute object in Action category is not a JSON array although it should, according to 4.2.4.

b.    typo: “ AttributeId” (one space too many) instead of “AttributeId” for the location attribute of AccessSubject.


3.       Security consideration: the attribute Value and Content items can be any arbitrary object of arbitrary depth and/or string of arbitrary length, resulting in possible denial of service from the PDP. I think the spec should mention this issue somewhere (like section 9 in XACML 3.0). On a side node, section 9 of XACML 3.0 could also mention the same kind of issue with AttributeValues or Attributes/Content possibly containing arbitrary XML elements of excessive depth or text size.

Kind regards,




Cyril Dangerville

Security Engineer, CISSP

Thales Services



From: Chet Ensign [mailto:chet.ensign@oasis-open.org]
Sent: mardi 7 novembre 2017 21:12
To: tc-announce@lists.oasis-open.org; members@lists.oasis-open.org; xacml@lists.oasis-open.org; xacml-comment@lists.oasis-open.org; idtrust-ms@lists.oasis-open.org
Subject: [xacml-comment] 60-day Public Review for REST Profile of XACML 3.0 and JSON Profile of XACML 3.0 COS01 - ends January 6th


OASIS Members and other interested parties, 


Members of the OASIS eXtensible Access Control Markup Language (XACML) TC [1] have recently approved Special Majority Ballots [2] to advance REST Profile of XACML 3.0 Version 1.0 and JSON Profile of XACML 3.0 Version 1.0 as Candidate OASIS Standards (COSs). These COSs now enter a 60-day public review period in preparation for the member call for consent for OASIS Standards.


The REST Profile specification defines a profile for the use of XACML in a RESTful architecture. The TC received 4 Statements of Use from Oracle, EMC, Axiomatics, and NextLabs [3].


The JSON profile proposes a standardized interface between a policy enforcement point and a policy decision point using JSON, leveraging the decision request and response structure specified in the core XACML standard. The TC received 3 Statements of Use from ViewDS Identity Solutions, Axiomatics AB, and NextLabs [4]. 


The Candidate OASIS Standards are available at: 


- REST Profile of XACML v3.0 Version 1.0 

Candidate OASIS Standard 01 

12 October 2017 


Editable source (Authoritative): 






- JSON Profile of XACML 3.0 Version 1.0 

Candidate OASIS Standard 01 

12 October 2017 


Editable source (Authoritative): 






ZIP distribution file (complete):


For your convenience, OASIS also provides ZIP files of each of the COS. You can obtain the ZIP files at: 


REST Profile of XACML 3.0: 


JSON Profile of XACML 3.0: 


Public Review Period:


This 60-day public review starts 08 November 2017 at 00:00 UTC and ends 06 January 2017 at 23:59 UTC.


This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.


Additional information about the specification and the XACML TC may be found at the TC's public home page:



Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility as explained in the instructions located via the button labeled "Send A Comment" at the top of the TC public home page, or directly at:



Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:



All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with these public reviews of “REST Profile of XACML 3.0 V1.0" and "JSON Profile of XACML 3.0 V1.0,” we call your attention to the OASIS IPR Policy [5] applicable especially [6] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member's patent, copyright, trademark and license rights that read on an approved OASIS specification. 


OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC's work.




[1] OASIS eXtensible Access Control Markup Language (XACML) TC      


[2] Approval ballots: 


[3] Statements of Use for REST Profile of XACML 3.0






[4] Statements of Use for JSON Profile of XACML 3.0






RF on Limited Terms Mode




Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]