NiFi Ingest 26.1
NiFi Ingest

# Document Security Example

This section demonstrates how to set up mapped security to protect information that was extracted from a SharePoint repository, using the GetSharePoint processor.

Groups in SharePoint or SharePoint Online can originate from multiple sources, for example from SharePoint itself or from an on-premise Active Directory. This means that you must retrieve group information from both sources. The GetSharePointGroups processor retrieves SharePoint groups, and you can retrieve groups from Active Directory using the OmniGroupServer LDAP module. Finally, OmniGroupServer must be configured to combine the groups retrieved from both sources into a single repository.

To configure mapped security you must set up the following components:

- Content and Community. You must set up the Content component to identify the security type associated with each document. You must also configure the Community component, so that it sends a security token to the front-end application when a user logs on. For information about how to set up these components, refer to the Document Security Administration Guide.

- OmniGroupServer.

  - Create a repository in OmniGroupServer, to contain the SharePoint group information extracted by the GetSharePointGroups processor and sent to OmniGroupServer by the PutOGS processor.
  - Create a repository in OmniGroupServer to contain group information from Active Directory, and configure OmniGroupServer to retrieve the groups thorough LDAP.
  - Create another repository, and configure OmniGroupServer to combine the SharePoint and Active Directory groups.

  Only the final repository, that contains the combined information, should be queried by Community to populate user security info strings. For information about how to configure OmniGroupServer, see Configure OmniGroupServer.

  TIP: For many security types, you might only need to create an empty repository to be populated with group information by the PutOGS processor that you configure in NiFi.

- NiFi Ingest.

  - Set up NiFi Ingest connectors to include security information (Access Control Lists) in documents. You must also add a field to each document that identifies the security type. For information about how to do this, see Configure the NiFi Ingest Connector.
  - Add a PutOGS processor to your dataflow, to send the group information that is retrieved by the connector to your OmniGroupServer. For information about how to do this, see Send Group Information to OmniGroupServer.
- A front-end application for querying Knowledge Discovery. For information about how to configure the front-end application, refer to its documentation.

Copyright 2018-2025 Open Text
Version 26.1 | Last updated January 2026

Send documentation feedback

Close

Send documentation feedback

To send feedback using your default email client, open an email window.

Otherwise, send your feedback and the information below to MFI-swpdl.idoldocsfeedback@opentext.com.

We appreciate your feedback!

Product: Knowledge Discovery NiFi Ingest 26.1

Topic Title: Document Security Example