Hal,
No project yet but something that we would like to see and we are an Axiomatics shop.
John âMikeâ Davis
VHA Security Architect
760-632-0294
From: xacml@lists.oasis-open.org [mailto:xacml@lists.oasis-open.org]
On Behalf Of David Brossard
Sent: Tuesday, September 18, 2018 12:57 PM
To: Harold Lockhart <hal.lockhart@oracle.com>; DANGERVILLE Cyril <cyril.dangerville@thalesgroup.com>
Cc: xacml <xacml@lists.oasis-open.org>; xacml-comment@lists.oasis-open.org
Subject: [EXTERNAL] [xacml] Re: [xacml-comment] FW: Question with the XACML-REST namespace
Here what I can find:
-
Axiomatics Policy Server implements the REST interface
-
We know from Cyril (in cc) that AuthZForce does too
-
ViewDS? Steven I believe you do, right?
-
According to Google so does Balana (WSO2)
-
EU SUNFISH Project
-
Oracle Platform Security Services (OPSS)
That's all I could find. I will pass on the information to our development team. I doubt it's a major change. Also, it does not play an active part in the runtime authorization flow. I would be OK with the change.
I need to hear from as many organizations as possible who are implementing the REST Profile. As you can see below, the current namespace is not in accord
with Naming Directives. The question is: is it too late to change this?
If you are not comfortable answering publically for some reason, you can respond directly to the chairs.
Hal
From: Chet Ensign <chet.ensign@oasis-open.org>
Sent: Tuesday, September 18, 2018 12:58 PM
To: Hal Lockhart <hal.lockhart@oracle.com>; bill parducci <bill@parducci.net>
Cc: Paul Knight <paul.knight@oasis-open.org>
Subject: Question with the XACML-REST namespace
Paul came across the namespace for the XACML-REST specification yesterday and realized that it doesn't conform to the format in use.
Paul noted however that the namespace appears to be in use in a lot of implementations. He did a search in Google for "ns/xacml/relation" and got 114 hits.
So we'll leave it as is unless you tell us that it doesn't matter. If changing it won't break anything, we'll update it. But if it cause headaches and work for your user community,
then we'll leave it alone.
Can you just confirm to us either that we should leave it as is or that we can go ahead and change it, I'd appreciate it. We'll then have the issue documented for future publications.
--
Organized by The World Bank, OASIS, and Georgetown University
Chet Ensign
Chief Technical Community Steward
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
--
David Brossard
VP of Customer Relations
|