Knowledge Discovery 25.1
Document Security Administration Guide

# Configure Security Types

To configure security types

1. Open the Content component configuration file.

2. In the `[Security]` section, set the `SecurityInfoKeys` configuration parameter to the path of your AES key file.

   `[Security]
   SecurityInfoKeys=/path/to/aes.keyfile`

   This is used to encrypt and decrypt the security strings that Knowledge Discovery generates for each user. For this reason, the value of `SecurityInfoKeys` must be the same for each component that requires it (for example, Content, Community, and DAH must all use the same key file).

   If you need to generate a new key file, use the `autpassword` utility. Generate a key file in the same way as for encrypting passwords. For more information about using the `autpassword` utility, see Encrypt Passwords.

3. List the security types that you want to use. For example:

       [Security]
       SecurityInfoKeys=/path/to/aes.keyfile
       0=NT_V4
       1=Notes_V4
       ...

4. Create a new configuration section for each of the security types. In each section, set the following configuration parameters:

   Parameter | Value
   --- | ---
   `SecurityCode` | A unique number to use as an identifier for the security type.
   `Library` | The name of the security library to use to check the security settings of documents that use this security type.
   `Type` | The security type. Specify one of the security types listed in Security Types.
   `ReferenceField` | The name of the document field that stores the ACL for this security type. The default value of this parameter is `*/AUTONOMYMETADATA` (by default, connectors add the ACL to the `AUTONOMYMETADATA` field).
   `EscapedEntries` | Non-alphanumeric characters in a security string that is passed to the Content component are usually percent-encoded, but the names in the ACL are not. If the user or group names in the security string can contain non-alphanumeric characters, set this parameter to `true`. This instructs Content to expect escaped information, and ensures that the names are correctly unescaped to perform security checks. The default for this parameter for most security types is `false`; it is usually necessary to set it to `true`.

   For example:

       [NT_V4]
       SecurityCode=1
       Library=./modules/mapped_security
       Type=AUTONOMY_SECURITY_V4_NT_MAPPED
       ReferenceField=*/AUTONOMYMETADATA
       EscapedEntries=true

   For more information about the configuration parameters that you can set to customize security, refer to the Content component Help.

Copyright 2024 Open Text
Version 25.1 | Last updated January 2025

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 25.1

Topic Title: Configure Security Types