Add or Edit a Jive Server Source

When you have the required privileges, you can add the content of a Jive community to a Coveo organization.

Tip
Leading practice

The number of items that a source processes per hour (crawling speed) depends on various factors, such as network bandwidth and source configuration. See About Crawling Speed for information on what can impact crawling speed, as well as possible solutions.

Source Key Characteristics

Features Supported Additional information
Jive version 9

Only the minor versions currently maintained by Jive are supported. The latest version to have been tested with Coveo is 9.0.

Searchable content types check
  • Communities (also known as Spaces), social groups (also known as groups), projects, people and their profile, direct messages (requires Coveo plugin), items (private and public), discussions (private and public), blog posts (for spaces, projects, users, groups and system blogs), announcements, polls, comments (for items, blog posts, and polls), attachments (for items, blog posts, and discussions), ideas (private and public), and videos (private and public).

  • Support phrase substitutions (requires Coveo plugin), tags, and categories.

Content update operations Refresh check

Takes place every hour by default. A rescan or rebuild is required to retrieve:

  • Comments on comments and replies on replies

  • Deleted file items

The Coveo plugin is required to:

  • Remove recently deleted Jive items

  • Properly refresh discussions

Rescan check
Rebuild check
Content security options Determined by source permissions check

Requires the Coveo plugin.

Source creator check
Everyone check

Requirements

Before configuring your source, you must ensure that your Jive instance is ready to work with Coveo.

Supported Jive Version

The source supports Jive 9.

Coveo has dropped support for sources indexing Jive 6, 7, or 8 content, but these sources are typically still operational.

Jive Administrator Account

When you want to include Jive permissions, you must create a specific Jive administrator account with Full Access permissions that’s only used for the source.

Jive Server Accessible to Coveo

When the access to communication ports between Coveo and the Jive server is restricted, the appropriate port(s) must be opened in the network infrastructure such as in firewalls to allow Coveo to access the content.

Note

At least the following ports must be opened:

  • 443: standard port for secured internet connections (HTTPS)

  • 8080: Jive default port

Add or Edit a Jive Server Source

Before you start, ensure that your Jive instance meets the source requirements.

When adding a source, in the Add a source of content panel, click the On-Premises or the Crawling Module tab, depending on whether you need to use the Coveo On-Premises Crawling Module to retrieve your content. See Content Retrieval Methods for details.

To edit a source, on the Sources (platform-eu | platform-au) page, click the desired source, and then click Edit in the Action bar.

"Configuration" Tab

In the Add/Edit a Jive Server Source panel, the Configuration tab is selected by default. It contains your source’s general and authentication information, as well as other parameters.

General Information

Content Update and Security Requirement

Download and install the Coveo Jive plugin if you intend to select the Determined by source permissions content security option.

Note

If you use Jive 6, 7, or 8 download this plugin instead.

Source Name

Enter a name for your source.

Tip
Leading practice

A source name can’t be modified once it’s saved, therefore be sure to use a short and descriptive name, using letters, numbers, hyphens (-), and underscores (_). Avoid spaces and other special characters.

Instance URL

Enter the web address of the Jive instance that you want to index.

Starting Community

Optionally, enter the URL of a Jive Community where the crawling should begin. Coveo indexes the content of the communities (also known as spaces) under the starting community.

By default, the root community (also known as root space) is used.

Note

Content outside the starting community can be indexed thanks to the options in the Content to include section.

Paired Crawling Module

If your source is a Crawling Module source, and if you have more than one Crawling Module linked to this organization, select the one with which you want to pair your source. If you change the Crawling Module instance paired with your source, a successful rebuild is required for your change to apply.

Character Optical Recognition (OCR)

If you want Coveo to extract text from image files or PDF files containing images, check the appropriate box. OCR-extracted text is processed as item data, meaning that it’s fully searchable and will appear in the item Quick View. See Enable Optical Character Recognition for details on this feature.

Note

Contact Coveo Sales to add this feature to your organization license.

Allow Anonymous Access

Check this box to map the Everyone group in Jive to the Everyone group of the Email security identity provider.

Important

When you check this box, all items accessible to the Everyone group in Jive become public. In other words, any user (authenticated or anonymous) of your search interface can find these items in their search results.

"Authentication" Section

Enter the credentials of a Jive account with Full Access permissions to the Jive instance. See Source Credentials Leading Practices.

"Content to Include" Section

This section allows you to specify whether you want to index some additional types of content. Communities (also known as spaces), projects, social groups (also known as groups), and system blogs are indexed by default.

Note

By default, all Jive content is indexed, regardless of its status (except private users content under the Jive Community domain).

People

Check the People box to index user profiles, personal blogs, and private items (items and discussions). Private messages (also known as direct messages) aren’t included.

Important

Since it’s not possible to apply permissions to people items, we strongly recommend that you don’t check the People box. Your Jive user profiles probably contain private information, and checking this box would make this data available to all search interface users.

Moreover, enabling this parameter significantly increases the crawling time. If you need to index people content, you should create a separate Jive Server source specifically to index this content.

Published Items Only

Check this box if you want to index only the items whose status is Published.

Note

A source refresh catches Jive item status changes and respects the configuration of this parameter.

Active Directory Permissions

This option is available with Crawling Module sources only. If you’re creating or editing an source of type On-Premises, skip to "Content Security" tab.

When you check this box and provide the required Active Directory information in the fields that appear, Active Directory permissions are indexed and replicated in your search interface.

For this option to be enforced, you must also select the Determined by source permissions option in the Content Security tab.

Active Directory Username and Active Directory Password

Enter credentials to grant Coveo access to your Active Directory.

Expand Well-Known SIDs

Select this option if you want the users that are included in your Active Directory well-known security identifiers to be granted access to the indexed content. Expect an increase in the duration of the security identity provider refresh operation. Supported well-known SIDs are: Everyone, Authenticated Users, Domain Admins, Domain Users, and Anonymous Users.

Tip
Leading practice

If your entire content is secured with the Everyone or Authenticated users well-known, it’s more cost-effective resource-wise to index it with a source whose content is accessible to everyone than to expand the well-known with a source that indexes permissions.

Enable TLS

Select this option to use a TLS protocol to retrieve your security identities. If you do, we strongly recommend selecting StartTLS if you can. Since LDAPS is a much older protocol, you should only select this value if StartTLS is incompatible with your environment.

Email Attributes

By default, Coveo retrieves the email address associated to each security identity from the mail attribute. Optionally, you can specify additional or different attributes to check. Should an attribute contain more than one value, Coveo uses the first one.

"Content Security" Tab

Select who will be able to access the source items through a Coveo-powered search interface. For details on this parameter, see Content Security.

Important

When using the Everyone content security option, see Safely Apply Content Filtering for information on how to ensure that your source content is safely filtered and only accessible by intended users.

"Access" Tab

In the Access tab, set whether each group and API key can view or edit the source configuration (see Resource Access):

  1. If available, in the left pane, click Groups or API Keys to select the appropriate list.

  2. In the Access Level column for groups or API keys with access to source content, select View or Edit.

Completion

  1. Finish adding or editing your source:

    • When you want to save your source configuration changes without starting a build/rebuild, such as when you know you want to do other changes soon, click Add Source/Save.

      Note

      On the Sources (platform-eu | platform-au) page, you must click Launch build or Start required rebuild in the source Status column to add the source content or to make your changes effective, respectively.

    • When you’re done editing the source and want to make changes effective, click Add and Build Source/Save and Rebuild Source.

      Back on the Sources (platform-eu | platform-au) page, you can review the progress of your source addition or modification.

      Once the source is built or rebuilt, you can review its content in the Content Browser.

  2. Optionally, consider editing or adding mappings once your source is done building or rebuilding.

Safely Apply Content Filtering

The best way to ensure that your indexed content is seen only by the intended users is to enforce content security by selecting either the Source creator or Determined by source permissions option when available.

However, if you need to configure your source so that the indexed source content is accessible to Everyone, you should adhere to the following leading practices to ensure that your source content is safely filtered and only accessible by the appropriate users:

Following the above leading practices results in a workflow whereby the user query is authenticated server side via a search token that enforces the search hub from which the query originates, which can’t be modified by users or client-side code. The query then passes through a specific query pipeline based on a search hub condition, and the query results are filtered using the pipeline filter rules.

Configure Query Filters

Filter rules allow you to enter hidden query expressions to be added to all queries going through a given query pipeline. They’re typically used to add a field-based expression to the constant query expression (cq).

Example

You apply the @objectType=="Solution" query filter to the pipeline to which the traffic of your public support portal is directed. As a result, the @objectType=="Solution" query expression is added to any query sent via this support portal.

Therefore, if a user types Speedbit watch wristband in the searchbox, the items returned are those that match these keywords and whose objectType has the Solution value. Items matching these keywords but having a different objectType value aren’t returned in the user’s search results.

To learn how to configure query pipeline filter rules, see Manage Filter Rules.

Note

You can also enforce a filter expression directly in the search token.

Use Condition-Based Query Pipeline Routing

The most recommended and flexible query pipeline routing mechanism is condition-based routing.

When using this routing mechanism, you ensure that search requests are routed to a specific query pipeline according to the search interface from which they originate, and the authentication is done server-side.

To accomplish this:

  1. Apply a condition to a query pipeline based on a search hub value, such as Search Hub is Community Search or Search Hub is Agent Panel. This condition ensures that all queries that originate from a specific search hub go through that query pipeline.

  2. Authenticate user queries via a search token that’s generated server side and that contains the search hub parameter that you specified in the query pipeline.

Configure the Search Token

When using query filters to secure content, the safest way to enforce content security is to authenticate user queries using a search token that’s generated server side. For instance, when using this approach, you can enforce a search hub value in the search token. This makes every authenticated request that originates from a component use the specified search hub, and therefore be routed to the proper query pipeline. Because this configuration is stored server side and encrypted in the search token, it can’t be modified by users or client-side code.

Implementing search token authentication requires you to add server-side logic to your web site or application. Therefore, the actual implementation details will vary from one project to another.

The following procedure provides general guidelines:

Note

If you’re using the Coveo In-Product Experience (IPX) feature, see Implementing Advanced Search Token Authentication.

  1. Authenticate the user.

  2. Call a service exposed through Coveo to request a search token for the authenticated user.

  3. Specify the userIDs for the search token, and enforce a searchHub parameter in the search token.

Note

You can specify other parameters in the search token, such as a query filter.

For more information and examples, see Search Token Authentication.

What’s Next?

What's next for me?