Appkit SDK Release Notes

Latest Release: 4.6.0 (27 September 2019)

Fusion comes bundled with everything you need to get started.

New features

No new features are included in this release.

Previous releases

4.5.0 (19 August 2019)

Appkit now supports role-based authorization with multiple roles. Previously, it was possible to define only a single, global role-based authorisation filter.

Create authorisation filters

Create multiple configuration files for role-based access in the security/access folder. Each file defines a single authorisation filter. When Appkit considers whether a specific user can access a specific resource, Appkit evaluates all of the filters.

Note
A best practice is to create authorisation filters that don’t overlap, that is, that don’t refer to the same resources.

You must give users access to resources explicitly by referencing one or more of their roles. A user who has none of the roles mentioned in the authorisation-filter files can’t access any resources.

If a user has multiple roles that specify different access to a resource, then the rule that denies access wins.

4.4.0 (22 July 2019)

The Elasticsearch search platform now supports geo-filtering and sorting based on distance.

Previously, the Appkit filter syntax supported a small number of simple data types (string, boolean, integer, double, and date) and ranges over simple data types.

With this release, the Appkit filter syntax adds support for an object data type that can specify filters of arbitrary complexity. The object data type uses JSON syntax to describe the data. For example, a filter can specify unordered lists of name/value pairs (objects) and ordered collections of values (arrays).

For example:

data[{"property1":"some_text","property2":34,"property3":true,"property4":9223372036854775807,"property5":53.4678,"property6":["a","b"],"property7":{"key1":"value","key2":56}}]["A filter object"]

4.3.0 (29 May 2019)

  • JWT authorisation against Fusion is supported – Appkit now supports JSON Web Token (JWT) authorisation against a Fusion JWT realm.

    For information about options for authorisation in Fusion, see Fusion authorisation.

  • Role-based authorisation – Appkit adds an authorisation filter that can authorise requests for protected resources based on the roles associated with the user who made the request. Security providers (such as SAML) or LDAP lookups can provide the roles.

    For information, see Role-based authorisation.

  • Solr JSON range facets – Appkit now supports Solr JSON range facets as follows:

    • Appkit can now parse facets that were generated using JSON syntax and leverage them for display purposes in Appkit UI components.

    • Appkit can’t generate JSON facet query syntax (which needs to be manually input in the query pipeline or as query custom parameters).

    • Appkit can’t use the JSON facet’s filters to further refine query.

  • Retrieval of properties by workflow platforms – If a platform is configured to be a workflow platform, platform property retrieval proceeds as follows:

    1. Appkit checks to see whether the workflow platform has a property.

    2. If the workflow platform doesn’t have the property, Appkit checks to see whether the underlying platform has the property.

    3. If both the workflow platform and the underlying platform have the same property, the one defined for the workflow takes precedence.