Mapped Security with SharePoint and SharePoint Online

The SharePoint Remote Connector can retrieve information from SharePoint on-premise servers and SharePoint Online. This section explains how you might configure Mapped Security if you retrieve information from both sources.

When you retrieve documents from both sources the configuration can be more complex because the users and groups that the connector adds to ACLs can be in different formats. Typically, ACLs in documents retrieved from SharePoint have users and groups in NT-style (such as DOMAIN\USER or DOMAIN\GROUP) formats. In ACLs in documents retrieved from SharePoint Online, it can be more convenient to identify users and groups by email address.

A single IDOL user could therefore be identified in some ACLs by an NT-style user or group name or by an e-mail address. However, OmniGroupServer and the IDOL Community component can only associate one user name with each security type. As a result, Micro Focus recommends configuring separate security types for SharePoint on-premise and SharePoint Online. In general, all of the documents that belong to a specific security type should have ACLs that are formatted in a consistent way.

Having separate security types for SharePoint on-premise and SharePoint Online will affect the configuration of several components including the SharePoint Remote Connector, OmniGroupServer, IDOL Community, and IDOL Content.

Connector Configuration

When you configure the connector, configure the fetch tasks that retrieve information from SharePoint and SharePoint Online to add a different security type to documents. For example:

[SharePointOnPremise]
...
MappedSecurity=TRUE
UseEmailAsGroupName=FALSE
IngestActions=META:SecurityType=SharePoint

[SharePointOnline]
...
MappedSecurity=TRUE
UseEmailAsGroupName=TRUE
IngestActions=META:SecurityType=SharePointOnline

OmniGroupServer Configuration

When you configure OmniGroupServer, define separate repositories for SharePoint on-premise users and groups, and SharePoint Online users and groups. For example, you might configure:

Only the repositories that contain the combined information should be queried by IDOL Community.

For information about how to configure these repositories, see Retrieve Security Group Information using OmniGroupServer.

IDOL Server Configuration

For more information about configuring security types in the IDOL Content and IDOL Community components, refer to the IDOL Document Security Administration Guide.


_FT_HTML5_bannerTitle.htm