# Configure Security in Fact Bank

You can use IDOL mapped security with Fact Bank, by including the ACL information in your SQL backend fact store.

To use IDOL mapped security with Fact Bank you must:

- configure the appropriate security types in your Answer Server configuration file.
- uses a `sources` table in your SQL database fact store, with the ACL values.
- add a `security_types` table in your SQL database fact store, with the details of the security types.

## Configure the Security Types in Answer Server

Security configuration in Answer Server is similar to the configuration in the IDOL Content component. Depending on your data sources, it is likely that your Answer Server security configuration contains the same security types as your IDOL Content component data store.

You do not need any additional security libraries to run security in Answer Server fact bank.

To configure security in Answer Server

1. Open your configuration file in a text editor.

2. Find the `[Security]` configuration section, or add one if it does not exist.

3. In the `[Security]` section, set the `SecurityInfoKeys` parameter to specify the security encryption keys to use to encrypt and decrypt the security information. You can set the `SecurityInfoKeys` parameter either to the name of an AES key file (recommended) or to a comma-separated list of four signed 32-bit integers. For information about how to generate a key file with the `autpassword` command-line tool, refer to the IDOL Server Administration Guide.

   For example:

       [Security]
       SecurityInfoKeys=MyAESKeyFile.ky

4. In the `[Security]` section, list the security types that you want to use.

       0=NT
       1=Netware
       2=Notes
       3=Exchange

5. Create a section for each of the security types you defined (the section must have the same name as the security type). For each section, provide settings that determine how Answer Server handles that security type. For example:

       [NT]
       Type=AUTONOMY_SECURITY_V4_NT_MAPPED

       [Netware]
       Type=AUTONOMY_SECURITY_NETWARE_MAPPED

       [Notes]
       Type=AUTONOMY_SECURITY_V4_NOTES_MAPPED

       [Exchange]
       Type=AUTONOMY_SECURITY_EXCHANGE_MAPPED

6. Save and close the configuration file.

## Set Up Fact Store Tables for Security

To use mapped security with your facts, you must use the `sources` table in your SQL fact store.

The sources table contains details of the source for your facts. Each source has an ID, which you use in the facts table to identify the source for an individual fact. For example:

Facts Table
entity_code | property_code | property_value | qualifier_combination | source_id
--- | --- | --- | --- | ---
`COMPANY` | `CEO` | `Jane Smith` | 0 | 1

Sources Table
id | source
--- | ---
1 | `http//www.example.com/about`

When you use mapped security, the sources table also includes an access control list (ACL) for each source, and a security type ID. The security type ID corresponds to a row in the `security_types` table, which contains details of your configured security types.

For example:

Sources Table
id | source | acl | security_type_id
--- | --- | --- | ---
1 | `http//www.example.com/about` | 1:U:G:NU:9sjbyPA,9tnU38jBwfA:NG:9sjbxMHOwt/d8A | 3

Security_Types Table
id | friendly_name
--- | ---
1 | `Exchange`
2 | `Netware`
3 | `NT`

For more information about the tables in your SQL fact store, see Set Up a SQL Backend as Fact Store.

_FT_HTML5_bannerTitle.htm