Document level security: meta collections
Document level security can still be applied to documents within collections, even if those collections are searched from an overarching meta-collection. The meta collection can contain a mix of secured and unsecured collections.
The first step to take is to create the component collections as you would normally. (See the relevant pages for the type of collections you wish to create)
Important note: With the Modern UI, all the components of a meta collection must have authentication enabled (ui.modern.authentication) as these collection will be used to serve results).
- Ensure each component collection to be secured is properly set-up for document level security (Check the security.earlybinding.locks-keys-matcher.name and security.earlybinding.user-to-key-mapper parameters).
- Create a meta collection as you would normally. (See Meta collections)
- Include the appropriate component collections in the meta collection. (See Meta collections)
- Edit the Meta collection's
collection.cfg, and set security.earlybinding.user-to-key-mapper to
Meta. This will tell Funnelback to delegate user keys fetching to the plugins configured on each component (i.e.
Trim, ... depending on the component type).