Release Notes 2.4

Using the con terra Technologies Identity Service you can now authenticate smart.finder with ArcGIS Enterprise Portal and ArcGIS Online. This allows users to log in to smart.finder with their Portal or ArcGIS Online account using the OAuth 2.0 protocol.

As an alternative to the coupling with ArcGIS there is now also the possibility to connect your smart.finder installation with Keycloak. This type of authentication is also realised via a coupling with the con terra Technologies Identity Service.

With smart.finder 2.4.0 a Command Line Interface (CLI) is rolled out. This allows the interaction with the search index from the command line (e.g. Powershell or Unix Bash).

The CLI can be used primarily to migrate indexing jobs during a schema-update or to automate certain tasks.

It is now possible when displaying search results to choose between automatic scrolling or discrete paging, i.e. displaying the next X hits at the push of a button.

The display of sorting options for search results has been completely reworked. It is now easier to see by which field the hit list should be sorted in ascending/or descending order.

The fields on which searches are performed against the index can now be configured and weighted.

In the previous version of smart.finder, the search was always performed on one field as part of a full-text search. This is also the default setting in the current version.

This behavior can be configured per APp, so that e.g. on the field title and description is searched, but the results in title are evaluated higher.

For this purpose so-called query templates have been introduced.

With the current version, wildcard and phrase_search can be formulated from within an app. If needed, this behavior can be disabled by configuration.

You can now start several jobs simultaneously in the Job Manager. If jobs are in the scheduled or inactive state, they can be selected and transported to the indexer queue and processed in sequence.

A complete list of all changes can be found in the Changelog.

For security reasons, the administrator password in security mode INTEGRATED is no longer preset in the delivery. Set this using the security.user.admin.pw property to enable logging in to the smart.finder.

In indexingmanagement the index scheme has changed. Follow the information in migration guide for the version update.

In core0 the index scheme has changed. If you want to migrate the indexed documents from your current smart.finder installation, follow the migration instructions for the version update.

The SearchAnythingSearchTermResetAction component has been removed. You can now control the behaviour of the search with an empty search term through the searchAllOnEmptySearchTerm property of the ResultListPageForwarder component. See the sf_search-ui-connector bundle documentation for additional information.

Due to the new sorting component the configuration schema of the SortConfig component in the sf_resultlist bundle has been changed. So if you made adjustments to this component in your app.json files, see the sf_resultlist bundle documentation for details on how to update you configuration to the current schema.

In prior versions of smart.finder the cookie domain in the configuration property security.sso.cookie.domain required a leading dot. This dot is no longer supported. So specify the domain without a leading dot in compliance with RFC 6265. Example: