1. 03 May, 2022 1 commit
  2. 06 Apr, 2022 1 commit
  3. 27 Mar, 2022 11 commits
  4. 19 Mar, 2022 2 commits
  5. 14 Mar, 2022 1 commit
  6. 12 Mar, 2022 2 commits
  7. 11 Mar, 2022 1 commit
  8. 09 Mar, 2022 8 commits
  9. 08 Mar, 2022 1 commit
    • cdanger's avatar
      - Upgraded authzforce-ce-core-pdp-api to v21.1.1 · 44bb7668
      cdanger authored
      - Fixed bug when having multiple XPath expressions (e.g. AttributeSelectors) with XPath variables in the same Policy (the list of declared variables on Saxon XPathCompiler is internally saved and not reinitialized after each call to `XPathCompiler#compile(String)` having side effects when reusing the same XPathCompiler instance).
      44bb7668
  10. 07 Mar, 2022 2 commits
    • cdanger's avatar
      - Added SPIF-to-XACML conversion stylesheets: · 629cb21d
      cdanger authored
        - `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.
        - `spif2xacml-for-xpath-2.0.xsl`: SPIF-to-XACML policy transformation XSLT using XPath 2.0 features (not available in 1.0), with the option to enable AuthzForce optimizations (XSLT parameter `authzforce_optimized`) for further enhancements.
      
      - Used generated policies from sample ACME SPIF with above stylesheets to custom pdp tests XPath2.0 and XacmlVariablesAsXPathVariables.
      629cb21d
    • cdanger's avatar
      - Upgraded authzforce-ce-core-pdp-api: 21.1.0 · 38e46180
      cdanger authored
      - Replaced occurrences of XPathCompiler class in method parameters with Optional<XPathCompilerProxy>, XPathCompilerProxy being a new immutable class wrapping XPathCompiler (for safer code and fixing Spotbugs issues) from authzforce-ce-core-pdp-api, and the use of Optional to indicate it is used only if XPath is enabled (by PDP configuration or Policy(Set)Defaults/XPathVersion in enclosing Policy(Set) )
      - Added feature: XPath variables in AttributeSelectors' and `xPathExpression` `AttributeValues`s' XPath expressions can now be defined by XACML VariableDefinitions (variable name used as XACML VariableId), which means XACML Variables can be used as XPath variables there. And unit tests for it based on STANAG 4774.1
      - Fixed Spotbugs issues
      - VariableReference interface: added getXPathVariableName(): QName
      - Added unit tests for XPath 2.0 expressions in AttributeSelectors
      38e46180
  11. 25 Feb, 2022 1 commit
  12. 18 Feb, 2022 1 commit
  13. 08 Feb, 2022 1 commit
  14. 07 Feb, 2022 7 commits