Microsoft Planner Connector 26.2
Microsoft Planner Connector Help

# Configure Content and Community

This section describes the configuration changes that are required to enable mapped security for documents that originate from Microsoft Planner. For more information about configuring mapped security in the Content component and Community component, refer to the Document Security Administration Guide.

## Content Component

The first requirement is to add a field processing rule so that the Content component can determine whether a document is protected by Microsoft Planner security. Field processing rules are configured in the `[FieldProcessing]` section of the Content component configuration file.

The following example instructs the Content component to search for a field named `SECURITYTYPE` and check for the value `PLANNER`. You should have configured your Microsoft Planner Connector to add this field to every document (see Retrieve and Index Access Control Lists).

    [FieldProcessing]
    ...
    29=DetectSecurity_Planner

    [DetectSecurity_Planner]
    Property=SecurityOfficePlanner
    PropertyFieldCSVs=*/SECURITYTYPE
    PropertyMatch=PLANNER

    [SecurityOfficePlanner]
    SecurityType=OfficePlanner_V4

The `SecurityType` configuration parameter provides a name for the Microsoft Planner security type. This can be any string but you must use the same value in several other places, as described below.

After the Content component has determined that a document is protected by Microsoft Planner security, it must process the ACL that the Microsoft Planner Connector has added to the document in the `AUTONOMYMETADATA` field.

To process ACLs added to documents by the Microsoft Planner Connector, configure NT security (`Type=AUTONOMY_SECURITY_V4_NT_MAPPED`). Document security is configured in the `[Security]` section of the Content component configuration file. Create a new section with the same name that you specified with the `SecurityType` configuration parameter, above.

    [Security]
    ...
    6=OfficePlanner_V4

    [OfficePlanner_V4]
    SecurityCode=6
    Library=C:\IDOLServer/content/modules/mapped_security
    Type=AUTONOMY_SECURITY_V4_NT_MAPPED
    ReferenceField=*/AUTONOMYMETADATA

## Community Component

The final requirement is to configure user security so that when a user logs on to a front-end application, the Community component can return a security token that includes their group memberships. User security is configured in the `[Security]` section of the Community component configuration file.

Add a new section for Microsoft Planner, similar to the following example:

    [Security]
    7=OfficePlanner

    [OfficePlanner]
    DocumentSecurity=TRUE
    DocumentSecurityType=OfficePlanner_V4
    GroupServerHost=localhost
    GroupServerPort=3057
    GroupServerRepository=OfficePlanner
    SecurityFieldCSVs=username
    CaseSensitiveUserNames=FALSE
    CaseSensitiveGroupNames=FALSE

The value of the `DocumentSecurityType` parameter must match the value you set for the parameter `SecurityType` in the Content component configuration file.

The `GroupServerHost` and `GroupServerPort` parameters should specify the host name or IP address, and ACI port, of your OmniGroupServer. The `GroupServerRepository` parameter should specify the name of the repository that you created when you configured OmniGroupServer (see Retrieve User and Group Information).

Copyright 2026 Open Text
Version 26.2 | Last updated April 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 Microsoft Planner Connector 26.2

Topic Title: Configure Content and Community