Coveo for Sitecore 5 is now available!

No User has been Provided for the Search Request

Description

Querying on the search interface returns no results and triggers a Oops! Something went wrong with the server error instead.

When looking at the POST request to the Coveo server, the status is 200 but the response says No user has been provided for the search request.

Explanation

The Security Provider is not providing any valid user to Coveo, which suggests it is not configured correctly.

The cause could be that the name of the Security Provider is not specified correctly in the Coveo.SearchProvider.config file. This is more likely to happen on a CD server where the Security Provider’s name is not the same as on the CM server.

Otherwise, it could simply be that the Security Provider has not yet been instantiated.

Environment

  • Coveo for Sitecore

  • Security Provider

  • REST request

Resolution

If the Security Provider’s name differs from the one on the CM (this information is contained in the Coveo.SearchProvider.config file), it has to be changed so that both are the same.

If the Security Provider is not yet instantiated, you need to index any item or rebuild your index content. The Security Provider will be created during the first indexing operation.