Product DocsMenu

Configuring an Oracle Knowledge Security Provider

When you choose to index permissions associated with Oracle Knowledge items, the Coveo connector needs a security provider. When permissions are indexed, in Coveo search results, a user searching for Oracle Knowledge content only sees the content to which he has access in Oracle Knowledge.

Note: You can get familiar with how Coveo components deal with permissions on documents both at indexing and query time (see Security) .

To configure an Oracle Knowledge security provider

  1. On the Coveo server, access the Administration Tool (see Opening the Administration Tool).

  2. Select Configuration > Security.

  3. In the navigation panel on the left, click Security Providers.

  4. In the Security Providers page, click Add to create a new security provider.

  5. In the Modify Security Provider page:

    1. Configure the following required parameters:


      Choose a significant name to identify the security provider.

      Example: Oracle Knowledge Security Provider

      Security Provider Type

      Select Oracle Knowledge (x64).

      User Identity

      Select the Oracle Knowledge user identity that you created previously (see Oracle Knowledge Connector Deployment Overview) .

      The Oracle Knowledge server URL

      Enter the URL to the client API web service.

      Example: http://MyInquiraServer:8226.

      The connector auto-filled this URL with /imws/WebObjects/imws.woa/ws/RequestProcessor.

      The Oracle Knowledge repository name

      Enter the name of the Information Manager repository to index.

      Note: The repository name is the same value that you enter in the Repository box when you log in to you Oracle Knowledge Information Manager.

      Security Provider

      When you want to index Oracle Knowledge security permissions, select the security provider that you selected or created to allow this security provider to resolve and expand the groups (see Oracle Knowledge Connector Deployment Overview).

    2. Review the default value of the following check box:

      Whether to treat a banned user as inactive

      Whether to treat a banned user as inactive. By default, banned users are treat as active.

    3. Review if you need to change the default values for the following parameter:

      The Users and UserGroups cache expiration time

      Enter the time before a cached object is marked as expirated and must be reindexed. The default value is 60 min.

    4. Click Add Parameter when you want to show and change the value of advanced source parameters (see Modifying Hidden Oracle Knowledge Source Parameters).

    5. Leave the Allow Complex Identities cleared as it does not apply to this type of security provider.

    6. Click Apply Changes.

What's Next?

Configure and index an Oracle Knowledge source (see Configuring and Indexing an Oracle Knowledge Source).

People who viewed this topic also viewed