Product DocsMenu

Coveo Platform 7.0 >
Administrator Help > Troubleshooting > Security Provider Not Properly Configured

Security Provider Not Properly Configured

Symptom

You may notice in the Administration Tool Overview page that either of the following error message appears in the System State section:

  • A security provider is not properly configured.

  • Some security providers are not properly configured.

Open the CES Console to locate and review the error messages that indicate which security provider has a problem and what is the cause of the problem (see Using the CES Console).

Possible causes and solutions

  • Repository is not warmed up and the security provider failed to initialize

    When a security provider starts, it needs to access the specified repository to complete its initialization. When the repository takes too much time to respond, the security provider connection attempt times out.

    Example: When your Sitecore security provider starts following an over-night CES maintenance restart, your Sitecore server is not used much at this hour and IIS needs to reload the site to respond to the security provider requests. The security provider reaches the connection timeout. In the CES Console you see a message of the form:

    The security provider "[SecurityProviderName]" could not be contacted for registration: CGKNetwork::PacketChannel::CannotOpenChannelException: The system cannot find the file specified.

    1. Ensure that the repository is warmed up.

    2. In the Administration Tool, access the configuration page for the security provider that has the problem (Configuration > Security Providers).

    3. Click Apply Changes to launch a new initialization attempt.

    4. In the CES Console, review the security provider messages to ensure that it starts without errors.

  • Missing security provider parameter

    Example: In the CES Console, you see a message of the form:

    An error occurred while initializing the Blade "[SecurityProviderName]" (ID #[n]): Error: The Security Provider "ServerBaseAddress" parameter is missing.

    Review the configuration of the security provider to add the missing parameter with the appropriate value (see Adding or Modifying a Security Provider).

  • Bad configuration value

    Example: In the CES Console, you see a message of the form:

    An error occurred while initializing the Blade "[SecurityProviderName]" (ID #[n]): Unable to connect to this address: 'http://YourRepositoryServer/'

    Review the configuration of the security provider to set a valid address for the server of your repository. If the address is correct, validate that the server is available (see Adding or Modifying a Security Provider).

    Example: The password for the Windows user referenced in the user identity assigned to a security provider changed in Active Directory but not in CES. In the CES Console, you see a message of the form:

    An error occurred while initializing the Blade "[SecurityProviderName]" (ID #[n]): Unexpected exception in method 'InitBlade': Coveo.Connectors.Sitecore2.Exceptions.Sitecore2WebServiceException`1[System.Exception]: Invalid username or password.

    Review the configuration of the security provider to ensure that the username and password of the assigned user identity are still valid (see Adding a User Identity).

People who viewed this topic also viewed