Funnelback patch 15.14.0.15

  • Released: 2018-08-31

  • Applies to: v15.14.0

  • Internal reference: SUPPORT-2717 FUN-3115

Description

  • Adds an option to padre-iw to allow control of how the lock string should be modified. The option is "-lock_string_mod_mode=[legacy raw]". By default it is set to "legacy" and that keeps the current behaviour of modifying the lockstring. The "raw" option results in padre-iw not altering the lock string; leaving in white space, new lines and commas.

  • Adds an experimental DLS plugin called "secBoolExpr" which is able to evaluate lockstrings which are boolean expression. For example, a lockstring where the user must have both B and C or A can be represented as "A,(B AND C)" or "A | (B&C)". This lockstring is evaluated as a boolean expression where the user keys are what is true in the expression. For example, if the user had "B" and "C" then they would be able to view that document. To enable the plugin set in collection.cfg "security.earlybinding.locks-keys-matcher.name=secBoolExpr" and set "-lock_string_mod_mode=raw" on the indexer.

Affected files

  • bin/padre-iw

  • bin/padre-iw.exe

  • lib/plugins/libsecBoolExpr.dll

  • lib/plugins/libsecBoolExpr.so

Deployment

  • (Windows) Stop currently running crawls.

  • Stop the Jetty web server and the Funnelback daemon.

  • Deploy the provided files on top of an existing install, backing up all replaced files.

  • Start the Jetty web server and the Funnelback daemon.

  • (15.14.0.14) The conf/<collection>/custom_gather.groovy of each Facebook collection that are failing to update due to Facebook API changes should be updated to have the content provided in share/custom_collection_templates/custom_gather.groovy.facebook. The customer will need to provide a never-expiring page access token to replace the app access token. Instructions on getting a never-expiring page access token can be found in the Funnelback Community Knowledgebase.

  • (Windows) Start crawls as needed.