blocks|key|1230195|text|也许我不理解这个问题，但是XACML的SAML概要文件不是做了您想要的吗？它定义了authzDecisionQuery和响应记录的SOAP格式，这应该就是您所需要的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1230196|我围绕着Sun/DISA的解释器(它在forge.mil上)构建了其中的一个，还有一个速度更快的版本(还没有发布)是围绕着一个完全编译的实现，它可以直接将XACML语言转换成Java代码。它的主要目标是可读性，而不是速度，但它的速度大约是它的十倍。|1230197|IMO+XACML可以工作，但作为一种让人难看的语言，它绝对是糟糕的。我更感兴趣的是找到一种特定于问题的语言来表达XACML的语义，以便人们能够理解它们。Java在这一点上击败了XACML，但Java作为一种特定于领域的语言相当笨拙。也许是Groovy？|1230198|PS:作为我们的第一次尝试，我们尝试了Attempto+Controlled+(ACE)。当我们发现ACE没有任何可行的方法来表达深度嵌套的条件(没有括号或大括号)时，我们很快就放弃了这个想法。尽管美国国家安全局对基于英语的政策语言有浓厚的兴趣，但我不确定英语是不是正确的想法。|1230199|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Maybe I don't understand the question, but doesn't the SAML profile for XACML do what you want? It defines SOAP formats for authzDecisionQuery and response records, which should be all you need for the WSDL.

I built one of these around Sun's interpreter for DOD/DISA (its on forge.mil), and a much faster version (not relesed yet) around a fully compiled implementation that directly transforms XACML into Java code. The main goal was readability, not speed, but its about ten times as fast.

IMO XACML works but is absolutely terrible as a language for people to look at. I'm more interested in finding a problem-specific language for expressing XACML's semantics so that people can understand them. Java beats XACML for this hands down, but Java's pretty clumsy as a domain-specific language. Perhaps Groovy?

PS: As our first shot at this we tried Attempto Controlled English (ACE). We quickly dropped that idea when we found ACE has nothing viable for expressing deeply nested conditionals (no parentheses or braces). And I'm not sure English was the right idea for this anyway, inspite of strong NSA interest in english-based policy languages.

blocks|key|4805797|text|Sun的XACML实现不是为您提供了可靠的API吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4805798|http://sunxacml.sourceforge.net/|offset|length|4805799|(开发已经回到正轨，网站应该很快就会更新。请看一下sunxacml-devl邮件列表。|4805800|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|W|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@$D|Q|E|R|1|S]]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]]]

Doesn't Sun's XACML Implementation give you a solid API?

<a href="http://sunxacml.sourceforge.net/" rel="nofollow noreferrer">http://sunxacml.sourceforge.net/</a>

(The development is back on track and the site should be updated soon. Hava a look at the sunxacml-devl mailing list.

blocks|key|3962590|text|sunxacml不是主动维护的。页面/实现的最后一次更新是在2006年。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3962591|HERAS-AF+XACML+Core是一个积极维护的开源XACML实现。|3962592|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

sunxacml is not actively maintained.
The last update on the page/implementation is from year 2006.

An actively maintained open source XACML implementation is the HERAS-AF XACML Core.

blocks|key|3962617|text|XACML和WS-XACML规范的SAML配置文件试图标准化XACML、PEP和PDP之间的通信。WSO2+Identity+Server是一个开源项目，将在明年初添加此支持。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3962618|谢谢..。|3962619|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

SAML profile for XACML and WS-XACML specifications are attempts to standardize the communication between XACML PEP and PDP. WSO2 Identity Server is an open source project and will adding this support by early next year..

Thanks...

blocks|key|1230250|text|不幸的是，WS-XACML早就死了。XACML的SAML概要是目前唯一的标准化方法，但这更多的是关于通信而不是API的易用性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1230251|在Axiomatics，我们确实开发了一个简单的SDK，但它仍然是我们的特定于供应商的。|1230252|我知道甲骨文和Nextlabs推动了一项名为OpenAZ的强有力的倡议。他们的目标是为PEP定义更简单的API。这可能是您想要查看的内容。|1230253|链接：|1230254|1230255|Axiomatics简单开发工具包演示：http://www.youtube.com/watch?v=Z_2M775uFxo|unordered-list-item|offset|length|1230256|OpenAZ：http://openliberty.org/wiki/index.php/OpenAz_Main_Page|1230257|1230258|詹姆斯我会认真看着OpenAZ的。每隔一周的星期四有一个电话会议，欢迎您参加。|1230259|entityMap|0|LINK|mutability|MUTABLE|url|http://www.youtube.com/watch?v=Z_2M775uFxo|1|http://openliberty.org/wiki/index.php/OpenAz_Main_Page^0|0|0|0|0|0|K|16|0|0|7|1I|1|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|17|8|@]|9|@$L|18|M|19|1|1A]]|A|$]]|$1|N|3|O|5|K|7|1B|8|@]|9|@$L|1C|M|1D|1|1E]]|A|$]]|$1|P|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1G|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]|10|$5|V|W|X|A|$Y|11]]]]

WS-XACML is long dead unfortunately. SAML profile of XACML is today the only standardized approach but that's more about the communication than the ease of use of APIs.

At Axiomatics we did develop a simple SDK but it remains our fairly vendor-specific.

I know that there is a strong initiative called OpenAZ pushed forward by Oracle and Nextlabs. They are aiming at defining simpler APIs for PEPs. That is probably what you would want to look at.

Links:

<ul>
<li>Axiomatics simple SDK demo: <a href="http://www.youtube.com/watch?v=Z_2M775uFxo" rel="nofollow">http://www.youtube.com/watch?v=Z_2M775uFxo</a></li>
<li>OpenAZ: <a href="http://openliberty.org/wiki/index.php/OpenAz_Main_Page" rel="nofollow">http://openliberty.org/wiki/index.php/OpenAz_Main_Page</a></li>
</ul>

James, I would seriously look at OpenAZ. There is a call every other week on Thursdays which you are welcome to attend.

Currently, the XACML specification defines a protocol for request / response but leaves it up to interpretation as to how it can be integrated into an enterprise application. I believe that the value of XACML won't be realized unless there is the creation of a new open source project that attempts to develop/standardize around a set of common APIs.

For those who are familiar with XACML, I would love to understand their first reactions to creation of such a project, whether they would be willing to contribute and what they believe an XACML API would look like?

Designing an XACML API

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

目前，XACML规范定义了一个用于请求/响应的协议，但如何将其集成到企业应用程序中则由它来解释。我认为，除非创建一个新的开源项目，尝试围绕一组通用API开发/标准化XACML，否则XACML的价值将无法实现。对于那些熟悉XACML的人，我很想了解他们创建这样一个项目的第一反应，他们是否愿意贡献，以及他们认为XACML API会是什么样子？

问设计XACML API
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问设计XACML APIEN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问设计XACML API
EN