Skip to content

Latest commit

 

History

History
356 lines (263 loc) · 37.1 KB

README.md

File metadata and controls

356 lines (263 loc) · 37.1 KB
Raw

Codacy Badge CII Best Practices Build Status FOSSA Status

Javadocs: PDP engine Javadocs, XACML/JSON extension Javadocs, Test utilities Javadocs

AuthzForce Core (Community Edition)

Authorization PDP (Policy Decision Point) engine implementing the OASIS XACML v3.0.

AuthzForce Core may be used in the following ways:

  • Java API: you may use AuthzForce Core from your Java code to instantiate an embedded Java PDP.
  • CLI (Command-Line Interface): you may call AuthzForce Core PDP engine from the command-line (e.g. in a script) by running the provided executable.

HTTP/REST server: if you are interested in using an HTTP/REST API compliant with REST Profile of XACML 3.0, check the AuthzForce RESTful PDP project and AuthzForce server project.

Features

Compliance with the following OASIS XACML 3.0 standards

For further details on what is actually supported regarding the XACML specifications, please refer to the conformance tests README.

Enhancements to the XACML standard

Interfaces

  • Java API: basically a library for instantiating and using a PDP engine from your Java (or any Java-compatible) code;
  • CLI (Command-Line Interface): basically an executable that you can run from the command-line to test the engine; HTTP/REST API compliant with REST Profile of XACML 3.0 is provided by AuthzForce RESTful PDP project for PDP only, and AuthzForce server project for PDP and PAP with multi-tenancy.

Safety & Security

  • Prevention of circular XACML policy references (PolicyIdReference/PolicySetIdReference) as mandated by XACML 3.0;
  • Control of the maximum XACML PolicyIdReference/PolicySetIdReference depth;
  • Prevention of circular XACML variable references (VariableReference) as mandated by XACML 3.0;
  • Control of the maximum XACML VariableReference depth.

Performance:

  • Optional strict multivalued attribute parsing: if enabled, multivalued attributes must be formed by grouping all AttributeValue elements in the same Attribute element (instead of duplicate Attribute elements); this does not fully comply with XACML 3.0 Core specification of Multivalued attributes (§7.3.3), but it usually performs better than the default mode since it simplifies the parsing of attribute values in the request.
  • Optional strict attribute Issuer matching: if enabled, AttributeDesignators without Issuer only match request Attributes without Issuer (and same AttributeId, Category...); this option is not fully compliant with XACML 3.0, §5.29, in the case that the Issuer is indeed not present on a AttributeDesignator; but it is the recommended option for better performance when all AttributeDesignators have an Issuer (the XACML 3.0 specification (5.29) says: If the Issuer is not present in the attribute designator, then the matching of the attribute to the named attribute SHALL be governed by AttributeId and DataType attributes alone.);
  • Optimal integer data-type implementation: the maxIntegerValue configuration parameter (expected maximum absolute value in XACML attributes of type http://www.w3.org/2001/XMLSchema#integer) helps the PDP choose the most efficient Java data-type. By default, the XACML/XML type http://www.w3.org/2001/XMLSchema#integer is mapped to the larger Java data-type: BigInteger. However, this may be overkill for example in the case of integer attributes representing the age of a person; in this case, the Short type is more appropriate and especially more efficient. Therefore, decreasing the maxIntegerValue value as much as possible, based on the range you expect your integer values to fit in, makes the PDP engine more efficient on integer handling: lower memory consumption, faster computations.
  • Pluggable Decision Cache: you can plug in your own XACML Decision Cache mechanism to speed up evaluation of (repetitive) requests. See down below for more info (Decision Cache extension).

Extensibility points

  • Attribute Datatypes: you may extend the PDP engine with custom XACML attribute datatypes;

  • Functions: you may extend the PDP engine with custom XACML functions;

  • Combining Algorithms: you may extend the PDP engine with custom XACML policy/rule combining algorithms;

  • Attribute Providers a.k.a. PIPs (Policy Information Points): you may plug custom attribute providers into the PDP engine to allow it to retrieve attributes from other attribute sources (e.g. remote service) than the input XACML Request during evaluation;

  • Request Preprocessor: you may customize the processing of XACML Requests before evaluation by the PDP core engine, e.g. used for supporting new XACML Request formats, and/or implementing XACML v3.0 Multiple Decision Profile Version 1.0 - Repeated attribute categories;

    Built-in Request Preprocessors (possible requestPreproc values in a PDP configuration):

    • For XACML/XML input (Java type oasis.names.tc.xacml._3_0.core.schema.wd_17.Request):
      • urn:ow2:authzforce:feature:pdp:request-preproc:xacml-xml:default-lax: implements only XACML 3.0 Core (no support for Multiple Decision Profile) and allows duplicate with same meta-data in the same element of a Request (complying with XACML 3.0 core spec, §7.3.3)
      • urn:ow2:authzforce:feature:pdp:request-preproc:xacml-xml:default-strict: implements only XACML 3.0 Core (no support for Multiple Decision Profile) and does not allow duplicate <Attribute> with same meta-data in the same <Attributes> element of a Request (not complying with XACML 3.0 core spec, §7.3.3, but better performances)
      • urn:ow2:authzforce:feature:pdp:request-preproc:xacml-xml:multiple:repeated-attribute-categories-lax: implements Multiple Decision Profile, section 2.3 (repeated attribute categories), and allows duplicate <Attribute> with same meta-data in the same <Attributes> element of a Request (complying with XACML 3.0 core spec, §7.3.3)
      • urn:ow2:authzforce:feature:pdp:request-preproc:xacml-xml:multiple:repeated-attribute-categories-strict: same as previous one, except it does not allow duplicate <Attribute> with same meta-data in the same <Attributes> element of a Request (not complying with XACML 3.0 core spec, §7.3.3, but better performances).
    • For XACML/JSON input as defined by JSON Profile of XACML 3.0 (Java type org.json.JSONObject), we have the equivalent to the above for XML, except xml is replaced with json in the identifier, and they require the extra Maven dependency authzforce-ce-core-pdp-io-xacml-json. Here is the list:
      • urn:ow2:authzforce:feature:pdp:request-preproc:xacml-json:default-lax;
      • urn:ow2:authzforce:feature:pdp:request-preproc:xacml-json:default-strict;
      • urn:ow2:authzforce:feature:pdp:request-preproc:xacml-json:multiple:repeated-attribute-categories-lax
      • urn:ow2:authzforce:feature:pdp:request-preproc:xacml-json:multiple:repeated-attribute-categories-strict.

  • Result Postprocessor: you may customize the processing of XACML Results after evaluation by the PDP engine, e.g. used for supporting new XACML Response formats, and/or implementing XACML v3.0 Multiple Decision Profile Version 1.0 - Requests for a combined decision;

  • Policy Provider: you may plug custom policy providers into the PDP engine to allow it to resolve PolicyIdReference or PolicySetIdReference;

  • Decision Cache: you may extend the PDP engine with a custom XACML decision cache, allowing the PDP to skip evaluation and retrieve XACML decisions from cache for recurring XACML Requests;

  • Java extension mechanism to switch HashMap/HashSet implementations (e.g. to get different performance results).

PIP (Policy Information Point)

AuthzForce provides XACML PIP features in the form of extensions called Attribute Providers. More information in the previous list of Extensibility points.

Limitations

XACML 2.0 support and migrating to XACML 3.0

As mentioned in the Features section, we do not support XACML 2.0 but only XACML 3.0, and we strongly recommend you migrate to XACML 3.0 as XACML 2.0 has become obsolete. In order to help you in the migration from XACML 2.0 to 3.0, we provide a way to migrate all your XACML 2.0 policies to XACML 3.0 automatically by applying the XSLT stylesheets in the migration folder. First download the stylesheets xacml2To3Policy.xsl and xacml3-policy-c14n.xsl from that folder, then apply them to your XACML 2.0 policy files using any XSLT engine supporting XSLT 2.0. For example, using SAXON-HE 9.x or later, you may do it as follows:

$ XACML_20_POLICY_FILE="policy.xml"
$  java -jar /path/to/Saxon-HE-10.3.jar -xsl:xacml2To3Policy.xsl -s:$XACML_20_POLICY_FILE -o:/tmp/${XACML_20_POLICY_FILE}.new
$  java -jar /path/to/Saxon-HE-10.3.jar -xsl:xacml3-policy-c14n.xsl -s:/tmp/${XACML_20_POLICY_FILE}.new -o:$XACML_20_POLICY_FILE.new

Optional XACML 3.0 features

The following optional features from XACML v3.0 Core standard are not supported:

  • Elements AttributesReferences, MultiRequests and RequestReference;
  • Functions urn:oasis:names:tc:xacml:3.0:function:xpath-node-equal, urn:oasis:names:tc:xacml:3.0:function:xpath-node-match and urn:oasis:names:tc:xacml:3.0:function:access-permitted;
  • Algorithms planned for future deprecation.

If you are interested in those, you can ask for support.

Versions

See the change log following the Keep a CHANGELOG conventions.

License

See the license file.

FOSSA Status

System requirements

Java (JRE) version: 17 LTS or later.

Usage

Getting started

CLI

Get the latest executable jar from Maven Central by following the authzforce-ce-core-pdp-cli link on the latest release page, and make sure you are allowed to run it (it is a fully executable JAR), e.g. with the following command (replace X.Y.Z with the current version):

$ chmod a+x authzforce-ce-core-pdp-cli-X.Y.Z.jar

To give you an example on how to test a XACML Policy (or PolicySet) and Request, you may copy the content of that folder to the same directory as the executable, and run the executable as follows:

$ ./authzforce-ce-core-pdp-cli-X.Y.Z.jar pdp.xml IIA001/Request.xml
  • pdp.xml: PDP configuration file in XML format, that defines the location(s) of XACML policy(ies) and more; for more information about PDP configuration parameters, the configuration format is fully specified and documented in the XML schema pdp.xsd, also available in a more user-friendly HTML form (start with the pdp element as the root element in a PDP configuration). Feel free to change the policy location to point to your own for testing.
  • Request.xml: XACML request in XACML 3.0/XML (core specification) format. Feel free to replace with your own for testing.

If you want to test the JSON Profile of XACML 3.0, run it with extra option -t XACML_JSON:

$ ./authzforce-ce-core-pdp-cli-X.Y.Z.jar -t XACML_JSON pdp.xml IIA001/Request.json
  • Request.json: XACML request in XACML 3.0/JSON (Profile) format. Feel free to replace with your own for testing.

For more info, run it without parameters, and you'll get detailed information on usage.

For troubleshooting, you can increase the log level of the logger(s) in the Logback configuration file logback.xml to INFO or DEBUG, esp. the logger named org.ow2.authzforce. Then run the CLI as follows (replace X.Y.Z with the current version):

$ java -jar -Dlogback.configurationFile=./logback.xml authzforce-ce-core-pdp-cli-X.Y.Z.jar pdp.xml IIA001/Request.xml

Java API

You can either build AuthzForce PDP library from the source code after cloning this git repository, or use the latest release from Maven Central with this information:

  • groupId: org.ow2.authzforce;
  • artifactId: authzforce-ce-core-pdp-engine;
  • packaging: jar.

Since this is a Maven artifact, and it requires dependencies, you should build your application with a build tool that understands Maven dependencies (e.g. Maven or Gradle), and configure this artifact as a Maven dependency, for instance with Maven in the pom.xml:

...
      <dependency>
         <groupId>org.ow2.authzforce</groupId>
         <artifactId>authzforce-ce-core-pdp-engine</artifactId>
         <version>${latest.version}</version>
      </dependency>
...

To get started using a PDP to evaluate XACML requests, the first step is to write/get a XACML 3.0 policy. Please refer to XACML v3.0 - Core standard for the syntax. For a basic example, see this one.

Then instantiate a PDP engine configuration with method PdpEngineConfiguration#getInstance(String). The required parameter confLocation must be the location of the PDP configuration file. For more information about PDP configuration parameters, the configuration format is fully specified and documented in the XML schema pdp.xsd, also available in a more user-friendly HTML form (start with the pdp element as the root element in a PDP configuration). Here is a minimal example of configuration:

<?xml version="1.0" encoding="UTF-8"?>
<pdp xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://authzforce.github.io/core/xmlns/pdp/8" version="8.1">
   <policyProvider id="policyProvider" xsi:type="StaticPolicyProvider">
     <policyLocation>${PARENT_DIR}/policy.xml</policyLocation>
   </policyProvider>
</pdp>

This is a basic PDP configuration with basic settings and the root policy (XACML 3.0 Policy document) loaded from a file policy.xml located in the same directory as this PDP configuration file (see previous paragraph for an example of policy).

As a result of calling method getInstance(...), you get a PdpEngineConfiguration object. Basic example of Java code using a PDP configuration file in some folder /opt/authzforce:

final PdpEngineConfiguration pdpEngineConf = PdpEngineConfiguration.getInstance("file:///opt/authzforce/pdp.xml");

Then the next step depends on the kind of decision request you want to evaluate. The various alternatives are detailed in the next sections.

Evaluating Requests in AuthzForce native API (most efficient)

If you are creating decision requests internally, i.e. directly from your Java code (not from any data serialization format), you'd better use AuthzForce native interface. You can pass the PdpEngineConfiguration to BasePdpEngine(PdpEngineConfiguration) constructor in order to instantiate a PDP engine. With this, you can evaluate a decision request (more precisely an equivalent of an Individual Decision Request as defined by the XACML Multiple Decision Profile) in AuthzForce's native model by calling evaluate(DecisionRequest) or (multiple decision requests with evaluate(List)). In order to build a DecisionRequest, you may use the request builder returned by BasePdpEngine#newRequestBuilder(...).

Basic example of Java code (based on previous line of code):

...
/*
 * Create the PDP engine. You can reuse the same for all requests, so do it only once for all.
 */
final BasePdpEngine pdp = new BasePdpEngine(pdpEngineConf);
...

// Create the XACML request in native model
final DecisionRequestBuilder<?> requestBuilder = pdp.newRequestBuilder(-1, -1);
/*
 * If you care about memory optimization (avoid useless memory allocation), make sure you know the (expected) number of XACML attribute categories and (expected) total number of attributes in the request, and use these as arguments to newRequestBuilder(int,int) method, instead of negative values like above.
 * e.g. 3 attribute categories, 4 total attributes in this case
 */
// final DecisionRequestBuilder<?> requestBuilder = pdp.newRequestBuilder(3, 4);

// Add subject ID attribute (access-subject category), no issuer, string value "john"
final AttributeFqn subjectIdAttributeId = AttributeFqns.newInstance(XACML_1_0_ACCESS_SUBJECT.value(), Optional.empty(), XacmlAttributeId.XACML_1_0_SUBJECT_ID.value());
final AttributeBag<?> subjectIdAttributeValues = Bags.singletonAttributeBag(StandardDatatypes.STRING, new StringValue("john"));
requestBuilder.putNamedAttributeIfAbsent(subjectIdAttributeId, subjectIdAttributeValues);

// Add subject role(s) attribute to access-subject category, no issuer, string value "boss"
final AttributeFqn subjectRoleAttributeId = AttributeFqns.newInstance(XACML_1_0_ACCESS_SUBJECT.value(), Optional.empty(), XacmlAttributeId.XACML_2_0_SUBJECT_ROLE.value());
final AttributeBag<?> roleAttributeValues = Bags.singletonAttributeBag(StandardDatatypes.STRING, new StringValue("boss"));
requestBuilder.putNamedAttributeIfAbsent(subjectRoleAttributeId, roleAttributeValues);

// Add resource ID attribute (resource category), no issuer, string value "/some/resource/location"
final AttributeFqn resourceIdAttributeId = AttributeFqns.newInstance(XACML_3_0_RESOURCE.value(), Optional.empty(), XacmlAttributeId.XACML_1_0_RESOURCE_ID.value());
final AttributeBag<?> resourceIdAttributeValues = Bags.singletonAttributeBag(StandardDatatypes.STRING, new StringValue("/some/resource/location"));
requestBuilder.putNamedAttributeIfAbsent(resourceIdAttributeId, resourceIdAttributeValues);

// Add action ID attribute (action category), no issuer, string value "GET"
final AttributeFqn actionIdAttributeId = AttributeFqns.newInstance(XACML_3_0_ACTION.value(), Optional.empty(), XacmlAttributeId.XACML_1_0_ACTION_ID.value());
final AttributeBag<?> actionIdAttributeValues = Bags.singletonAttributeBag(StandardDatatypes.STRING, new StringValue("GET"));
requestBuilder.putNamedAttributeIfAbsent(actionIdAttributeId, actionIdAttributeValues);

// No more attribute, let's finalize the request creation
final DecisionRequest request = requestBuilder.build(false);
// Evaluate the request
final DecisionResult result = pdp.evaluate(request);
if(result.getDecision() == DecisionType.PERMIT) {
	// This is a Permit :-)
	...
} else {
	// Not a Permit :-( (maybe Deny, NotApplicable or Indeterminate)
	...
}

See EmbeddedPdpBasedAuthzInterceptor#createRequest(...) method for a more detailed example. Please look at the Javadoc for the full details.

Evaluating Requests in XACML/XML format

You can pass the PdpEngineConfiguration to PdpEngineAdapters#newXacmlJaxbInoutAdapter(PdpEngineConfiguration) utility method to instantiate a PDP supporting XACML 3.0/XML (core specification) format (PdpEngineInoutAdapter<Request, Response>), with which you can evaluate XACML Requests by calling its evaluate(...) methods.

Evaluating Requests in XACML/JSON format

To instantiate a PDP supporting XACML 3.0/JSON (JSON Profile) format, you may reuse the test code from PdpEngineXacmlJsonAdapters, esp. the method PdpEngineXacmlJsonAdapters#newXacmlJsonInoutAdapter(PdpEngineConfiguration) which returns a PdpEngineInoutAdapter<JSONObject,JSONObject> on which you can call the evaluate(...) method with the JSON request as input.

You will need an extra dependency as well, available from Maven Central:

  • groupId: org.ow2.authzforce;
  • artifactId: authzforce-ce-core-pdp-io-xacml-json;
  • packaging: jar.
Evaluating Requests in other formats

You can support other non-XACML formats of access requests (resp. responses), including your own, by implementing your own Request Preprocessor (resp. Result Postprocessor ).

Logging

Our PDP implementation uses SLF4J for logging, so you can use any SLF4J implementation to manage logging. The CLI executable includes logback implementation, so you can use logback configuration file, e.g. logback.xml, for configuring loggers, appenders, etc.

Example of usage in a web service PEP

For an example of using an AuthzForce PDP engine in a real-life use case, please refer to the JUnit test class EmbeddedPdpBasedAuthzInterceptorTest and the Apache CXF authorization interceptor EmbeddedPdpBasedAuthzInterceptor. The test class runs a test similar to @coheigea's XACML 3.0 Authorization Interceptor test but using AuthzForce as PDP engine instead of OpenAZ. In this test, a web service client requests an Apache-CXF-based web service with a SAML token as credentials (previously issued by a Security Token Service upon successful client authentication) that contains the user ID and roles. Each request is intercepted on the web service side by a EmbeddedPdpBasedAuthzInterceptor that plays the role of PEP (Policy Enforcement Point in XACML jargon), i.e. it extracts the various authorization attributes (user ID and roles, web service name, operation...) and requests a decision from a local PDP with these attributes, then enforces the PDP's decision, i.e. forwards the request to the web service implementation if the decision is Permit, else rejects it. For more information, see the Javadoc of EmbeddedPdpBasedAuthzInterceptorTest.

Providing current-dateTime, current-date and current-time attributes

By default, the PDP provides the standard environment attributes specified in XACML 3.0 Core specification §10.2.5 (current-time, current-date and current-dateTime) only if they are not provided in the request (from the PEP). This behavior is compliant with XACML 3.0 standard which says (§10.2.5):

If values for these attributes are not present in the decision request, then their values MUST be supplied by the context handler.

Note that it does not say if and only if, therefore it is also possible and XACML-compliant to make the PDP use its own current-* values (current-time, etc.) all the time, regardless of the request values. This option is referred to as the override mode, and it is particularly useful when you do not trust the PEPs (requesters) to provide their own current date/time. You can enable this override mode by configuring an attributeProvider of type StdEnvAttributeProviderDescriptor with <override>true</override> in the PDP configuration, as you can see in this example (link). More information in the PDP configuration schema ( HTML form - select the tns:pdp element ).

Using Variables (VariableReference) in Target/Match

In XACML policies (Policy or PolicySet), as defined by the XACML schema, a <Match> may only include an AttributeValue and an AttributeDesignator or AttributeSelector; VariableReferences are not allowed, which makes it a limitation when you want to match a Variable (from a VariableDefinition) in a Target. AuthzForce provides a XACML-compliant workaround for this, which consists in enabling a XacmlVariableBasedAttributeProvider with a defined Category (see the PDP configuration XSD ( HTML form - select the tns:pdp element for the default Category). As a result, any <AttributeDesignator> in that Category is handled like a VariableReference, with the AttributeId used as VariableId.

The configuration of the XacmlVariableBasedAttributeProvider in the PDP is shown in this example (link) (attributeProvider of type XacmlVarBasedAttributeProviderDescriptor), applied to some Category urn:ow2:authzforce:attribute-category:vars. Then in the this policy sample (link), you can see an <AttributeDesignator Category="urn:ow2:authzforce:attribute-category:vars" AttributeId="var1" .../> which will be handled like <VariableReference VariableId="var1"/>.

Extensions

Experimental features (see Features section) are provided as extensions. If you want to use them, you need to use this Maven dependency (which depends on the authzforce-ce-core-pdp-engine already) instead:

  • groupId: org.ow2.authzforce;
  • artifactId: authzforce-ce-core-pdp-testutils;
  • packaging: jar

If you are still missing features in AuthzForce, you can make your own extensions/plugins (without changing the existing code), as described on the wiki.

If you are using the Java API with extensions configured by XML (Policy Providers, Attribute Providers...), you must use PdpEngineConfiguration#getInstance(String, String, String) to instantiate the PDP engine, instead of PdpEngineConfiguration#getInstance(String) mentioned previously. The two last extra parameters are mandatory in this case:

  1. catalogLocation: location of the XML catalog: used to resolve the PDP configuration schema and other imported schemas/DTDs, and schemas of any PDP extension namespace used in the configuration file. You may use the catalog in the sources as an example. This is the one used by default if none specified.
  2. extensionXsdLocation: location of the PDP extensions schema file: contains imports of namespaces corresponding to XML schemas of all XML-schema-defined PDP extensions to be used in the configuration file. Used for validation of PDP extensions configuration. The actual schema locations are resolved by the XML catalog parameter. You may use the pdp-ext.xsd in the sources as an example.

Editing and creating XACML 3.0 policies from scratch and from other formats

Using a full-fledged XML editor

For full support of XACML, you may use any XML editor supporting XML Schema. Make sure you import the XACML 3.0 schema into the tool and enable XML schema validation.

Using ALFA plugins for VScode - ALFA to XACML

Axiomatics provides an VScode plugin to edit policies in ALFA (Abbreviated Language for Authorization) and generate XACML 3.0 policies from it automatically. Beware of the Axiomatics license and limitations of ALFA with respect to XACML.

Similarly, Rock Solid Knowledge provides a VScode plugin for ALFA as well. Again, beware of the license.

From XACML 2.0 policies - XACML 2.0 to 3.0

If you still have legacy policies in older XACML 2.0 format, you can migrate to XACML 3.0 automatically with a simple command given in a previous section: https://github.com/authzforce/core#xacml-20-support-and-migrating-to-xacml-30

From SPIF (Security Policy Information File) - SPIF to XACML

A SPIF (Security Policy Information File) defines a security labeling policy in a XML document (based on the SPIF XML schema). More info on the Open XML SPIF website.

NATO ADatP-4774.1 - related to STANAG 4774 - gives implementation guidance on how to generate a XACML policy from a SPIF, including an example of XSLT stylesheet. We made a few improvements to that stylesheet, using the latest XACML 3.0 enhancements and AuthzForce optimizations, and differentiating READ and WRITE actions in accordance to the Bell-Lapadula model. The enhanced stylesheet is available in the spif-utils folder in two versions:

  • spif2xacml-for-xpath-1.0.xsl: SPIF-to-XACML policy transformation XSLT using XPath 1.0, more verbose and less efficient than the XPath 2.0 version below, available mostly for historical reasons (no longer maintained except bug fixing).
  • spif2xacml-for-xpath-2.0.xsl: SPIF-to-XACML policy transformation XSLT using XPath 2.0 features (not available in 1.0).

For example, you may generate the XACML policy from the sample ACME SPIF (from ADatP-4774.1) using XSLT engine of SAXON-HE 9.x or later on the command line as follows:

$ java -jar Saxon-HE-10.3.jar -xsl:spif-utils/spif2xacml-for-xpath-2.0.xsl -s:spif-utils/ACME-SPIF-example.xml -o:/tmp/ACME-XACML-policy.xml

In both cases, the generated XACML policy makes use of AttributeSelectors, so make sure your XACML engine supports those. In the case of AuthzForce, you need to set xPathEnabled="true" in the PDP configuration (pdp.xml) to enable support for AttributeSelectors, like in the XacmlVariableUsedAsXPathVariable test.

Support

You should use AuthzForce users' mailing list as first contact for any communication about AuthzForce: question, feature request, notification, potential issue (unconfirmed), etc.

If you are experiencing any bug with this project, and you indeed confirm this is not an issue with your environment (contact the users mailing list first if you are unsure), please report it on the OW2 Issue Tracker. Please include as much information as possible; the more we know, the better the chance of a quicker resolution:

  • Software version
  • Platform (OS and JRE)
  • Stack traces generally really help! If in doubt, include the whole thing; often exceptions get wrapped in other exceptions and the exception right near the bottom explains the actual error, not the first few lines at the top. It's very easy for us to skim-read past unnecessary parts of a stack trace.
  • Log output can be useful too; sometimes enabling DEBUG logging can help;
  • Your code & configuration files are often useful.

Security - Vulnerability reporting

See SECURITY.md.

Contributing

See CONTRIBUTING.md.

Adoption

If you are (or have been) using AuthzForce and would be so kind as to mention it here, please submit a pull request with your change to ADOPTERS.md.