AuthzForce Server provides a multi-tenant RESTful API to Policy Administration Points (PAP) and Policy Decision Points (PDP) supporting Attribute-Based Access Control (ABAC), as defined in the OASIS XACML 3.0 standard.

This project is part of FIWARE. For more information check the FIWARE Catalogue entry for Security.

Go to the releases page for specific release info: downloads (Linux packages), Docker image, release notes, and documentation.

The roadmap of this FIWARE GE is described here.

If you are interested in using an embedded XACML-compliant PDP in your Java applications, AuthzForce also provides a PDP engine as a Java library in Authzforce core project.

• Features
• Limitations
• Quality Assurance
• Install
• Documentation
• Training Courses
• Usage
• Testing
• Support
• Security
• Contributing
• License

• Compliance with the following OASIS XACML 3.0 standards:
  • XACML v3.0 Core standard
  • XACML v3.0 Core and Hierarchical Role Based Access Control (RBAC) Profile Version 1.0
  • XACML v3.0 Multiple Decision Profile Version 1.0 - Repeated attribute categories (urn:oasis:names:tc:xacml:3.0:profile:multiple:repeated-attribute-categories).
  • XACML v3.0 - JSON Profile Version 1.0, with extra security features:
    • JSON schema Draft v6 validation;
    • DoS mitigation: JSON parser variant checking max JSON string size, max number of JSON keys/array items and max JSON object depth.
  • GeoXACML 1.0.1. Supported as third-party extension from Secure Dimensions
  • Experimental support for:
    • XACML Data Loss Prevention / Network Access Control (DLP/NAC) Profile Version 1.0: only dnsName-value datatype and dnsName-value-equal function are supported;
    • XACML 3.0 Additional Combining Algorithms Profile Version 1.0: on-permit-apply-second policy combining algorithm;
    • XACML v3.0 Multiple Decision Profile Version 1.0 - Requests for a combined decision (urn:oasis:names:tc:xacml:3.0:profile:multiple:combined-decision).
• Safety/Security:
  • Prevention of circular XACML policy references (PolicySetIdReference) as mandated by XACML 3.0;
  • Control of the maximum XACML PolicySetIdReference depth;
  • Prevention of circular XACML variable references (VariableReference) as mandated by XACML 3.0;
  • Control of the maximum XACML VariableReference depth;
• 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 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.);
• 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;
  • 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.

AuthzForce provides XACML PIP features in the form of Attribute Providers. More information in the previous section.

• Policy management: create/read/update/delete multiple policies and references from one to another (via PolicySetIdReference)
• Policy versioning: create/read/delete multiple versions per policy.
• Configurable root policy ID/version: top-level policy enforced by the PDP may be any managed policy (if no version defined in configuration, the latest available is selected)
• Configurable maximum number of policies;
• Configurable maximum number of versions per policy.
• Optional policy version rolling (when the maximum of versions per policy has been reached, oldest versions are automatically removed to make place).

• Provides access to all PAP/PDP features mentioned in previous sections with possibility to have PDP-only instances (i.e. without PAP features).
• Multi-tenant: allows to have multiple domains/tenants, each with its own PAP/PDP, in particular its own policy repository.
• Conformance with REST Profile of XACML v3.0 Version 1.0
• Supported data formats, aka content types:
  • application/xml: XML based on API schema;
  • application/fastinfoset: Fast Infoset based on API's XML schema;
  • application/json: JSON based on API's XMLschema with a generic XML-to-JSON mapping convention
  • application/xacml+xml: XACML content only, as defined by RFC 7061
  • application/xacml+json: JSON format for XACML Request/Response on PDP only, as defined by XACML v3.0 - JSON Profile Version 1.0
• Defined in standard Web Application Description Language and XML schema so that you can automatically generate client code.

• Integration with file synchronization tools (e.g. csync2) or distributed filesystems (e.g. NFS and CIFS) to build clusters of AuthzForce Servers.

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.

This project is part of FIWARE and has been rated as follows:

• Version Tested:
• Documentation:
• Responsiveness:
• FIWARE Testing:

Every release is packaged in various types of distribution and the installation depends on the distribution type:

• Ubuntu/Debian package (recommended option): .deb. Use your usual Ubuntu/Debian APT to install the package;
• Other Linux distributions: .tar.gz for any Linux distribution. More info in the documentation;
• Docker image, installed/deployed with the usual docker container commands. See dist/src/docker/README.md for more info.

For download links, please go to the specific release page.

Once you downloaded the distribution of your preference, check the documentation for more information.

For links to the documentation of a release, please go to the specific release page.

• AuthzForce

The following tutorials on AuthzForce Server are available:

• 405. Identity Management - XACML Rule-based Permissions.
• 406. Identity Management - Administrating XACML Rules;

This section gives examples of usage and PEP code with a web service authorization module.

For an example of using an AuthzForce Server's RESTful PDP API in a real-life use case, please refer to the JUnit test class RESTfulPdpBasedAuthzInterceptorTest and the Apache CXF authorization interceptor RESTfulPdpBasedAuthzInterceptor. The test class runs a test similar to @coheigea's XACML 3.0 Authorization Interceptor test but using AuthzForce Server as PDP instead of OpenAZ. In this test, a web service client requests a 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 RESTfulPdpBasedAuthzInterceptor 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 with these attributes from a remote PDP provided by AuthzForce Server, 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 RESTfulPdpBasedAuthzInterceptorTest.

To run unit tests, install Maven and type

mvn test

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.

If you want to report a vulnerability, you can do so on this Github repository by following the process: Privately reporting a security vulnerability.

The sources for the manuals are located in fiware repository.

1. From the develop branch, prepare a release (example using a HTTP proxy):

$ mvn -Dhttps.proxyHost=proxyhostname -Dhttps.proxyPort=8080 jgitflow:release-start

2. Update the changelog with the new version according to keepachangelog.com.

3. Commit

4. Perform the software release (example using a HTTP proxy):

   $ mvn -Dhttps.proxyHost=proxyhostname -Dhttps.proxyPort=8080 jgitflow:release-finish

   If, after deployment, the command does not succeed because of some issue with the branches. Fix the issue, then re-run the same command but with 'noDeploy' option set to true to avoid re-deployment:

   $ mvn -Dhttps.proxyHost=proxyhostname -Dhttps.proxyPort=8080 -DnoDeploy=true jgitflow:release-finish

   More info on jgitflow: http://jgitflow.bitbucket.org/

5. Connect and log in to the Maven Central Repository: https://central.sonatype.com/

6. Go to Deployments and select the pending Deployment

7. Click the Publish button to release to Maven Central.

8. When the artifacts have been successfully published on Maven Central, follow the instructions in the Release section of fiware repository.

9. Build and publish the Docker image:

     $ git checkout master
     $ mvn clean package
     $ cd dist/target
     $ chmod +x release-docker.sh
     $ ./release-docker.sh

10. Update the versions in badges at the top of this file.

11. Create a release on Github with a description based on the release description template, replacing M/m/P with the new major/minor/patch versions.

This project is licensed under the terms of GPL v3 except Java classes in packages org.ow2.authzforce.webapp.org.apache.cxf.jaxrs.provider.json.utils and org.ow2.authzforce.webapp.org.codehaus.jettison.mapped which are under Apache License.

There is absolutely no problem in using a product licensed under GPL 3.0. Issues with GPL (or AGPL) licenses are mostly related with the fact that different people assign different interpretations on the meaning of the term “derivate work” used in these licenses. Due to this, some people believe that there is a risk in just using software under GPL or AGPL licenses (even without modifying it).

For the avoidance of doubt, the owners of this software licensed under an GPL 3.0 license wish to make a clarifying public statement as follows:

Please note that software derived as a result of modifying the source code of this software in order to fix a bug or incorporate enhancements is considered a derivative work of the product. Software that merely uses or aggregates (i.e. links to) an otherwise unmodified version of existing software is not considered a derivative work, and therefore it does not need to be released as under the same license, or even released as open source.