Skip to main content
Version: 7.2

Release notes

Table Attribute Connector features, bug fixes, and known issues by release date.

Version 7.2.0​

What's new​

  • JSON and YAML Schema support

    The Table Attribute Connector now supports configurations in both JSON and YAML formats, while maintaining compatibility with existing XML configurations. This update also allows support for attribute definitions in ALFA language when JSON or YAML is used for the configuration.

Fixed issues​

  • Corrected error handling for key attribute issuer mismatch

    Previously, a bug in the Table Attribute Connector caused the Access Decision Service (ADS) to return an HTTP 500 Error instead of the correct NotApplicable response. This occurred when the key attribute's issuer configured in the connector did not align with the key attribute's issuer present in the access request. This behavior has been fixed.

Version 7.1.1​

Fixed issues​

  • Security fixes

    A third-party library was updated to address the following security vulnerability: CVE-2023-44483Opens in a new tab.

Version 7.1.0​

What's new​

  • Table Attribute Connector supports lifecycle functionality

    The Table Attribute Connector now supports the lifecycle feature, which automatically releases used resources during domain refreshes and authorization engine shutdowns, preventing resource leakage. This feature is compatible with authorization engine versions that support lifecycle functionality but maintains backward compatibility with older versions that do not.

Known issues​

  • Attribute issuer mismatch causes 500 Error

    Due to a bug in Table Attribute Connector 7.1.0, Access Decision Service (ADS) throws an HTTP Error 500 instead of providing a NotApplicable response when the issuer of the attribute connector's key attribute doesn't match the respective issuer of the key attribute in the request.

Version 7.0.1​

What's new​

  • Vulnerability fixes

    Internal libraries were updated to address vulnerabilities.

  • Online documentation updates

    Documentation updates regarding the following:

    • Vulnerabilities report instructions

      Table Attribute Connector documentation is now updated with instructions on how to download vulnerabilities report from S3.

Version 7.0.0​

Fixed issues​

  • Table Attribute Connector incompatibility fixed

    Previously, the separately distributed Table Attribute Connector v. 6.x was not compatible with Axiomatics Services Manager and Axiomatics Policy Decision Point. This has been fixed.

Version 6.2.2​

Fixed issues​

  • Using a key attribute of integer type failed in PostgreSQL

    The removal of implicit casting in PostgreSQL version 8.3 caused the Table Attribute Connector to fail when a key attribute of integer type was used. This has been fixed by sending an integer instead of a string if the data type is integer.

Known issues​

  • Table Attribute Connector incompatibility

    The separately distributed Table Attribute Connector v. 6.x is not compatible with Axiomatics Services Manager up to version 6.2.8 and Axiomatics Policy Decision Point up to version 6.2.8, respectively. However, authorization domains built using ASM 6.2.8 and which contain configuration data for the Table Attribute Connector can be used with ADS and the v. 6.x attribute connector.

  • SQL Filter Service incompatibility

    The Table Attribute Connector 6.X does not work with SQL Filter Service 2.1.0 and earlier.

Version 6.1.0​

What's new​

  • Stability improvement

    The Table Attribute Connector no longer verifies the database connection on initialization. Transient database errors will not affect initialization of the attribute connector.

Version 6.0.0​

What's new​

  • Change of fully qualified name

    The fully qualified name for the TableAttributeFinder has been changed to com.axiomatics.attributeconnector.table.TableAttributeFinder. (The previous form was com.axiomatics.pip.table.TableAttributeFinder.)