Khoros Community Content Sources and the New CommunityGuard API Token

Hi everyone,

Khoros is rolling out CommunityGuard, a Cloudflare based edge protection layer, on Khoros hosted communities. This applies to both Khoros Classic and Khoros Aurora communities. Once it is enabled on your community, every API call to the Community API endpoints must carry an additional token in the request header. Requests without this token will be rejected with an HTTP 403 Forbidden error.

Who is affected

Any SearchUnify customer who has a Khoros community (Classic or Aurora) configured as a content source. The SearchUnify crawler uses the Khoros Community API to index your community content, so once CommunityGuard is active on your community, crawling will fail until one of the steps below is completed.

What happens if no action is taken

New and updated community content will stop getting indexed. Your existing indexed content stays searchable, but search results will gradually go stale.

What you need to do

Interim fix: Whitelist SearchUnify IP addresses

To keep crawling running without interruption, ask your Khoros administrator (or Khoros Support) to whitelist the SearchUnify IP addresses in CommunityGuard: Your SearchUnify CSM will assist you with the IP addresses.

This keeps your content source working while you arrange your token. Please note this is a temporary measure, not the long term setup.

Permanent fix: Request your CommunityGuard token and share it with us

• Reach out to your Khoros administrator or Khoros Support and request a CommunityGuard API token (sent in the x-khoros-api-access header) for API integrations.
• Share the token with SearchUnify Support or CSM. Please do not post tokens in the community.
• Our team will update your Khoros content source to use the token. No other change is needed on your side; your existing Basic Auth / OAuth credentials and permissions remain unchanged.

All customers will eventually need to move to the token based setup, even if IP whitelisting is in place.

What SearchUnify is doing

Our engineering team is updating the Khoros connector to support the new CommunityGuard header natively. We will share an update on this thread as soon as it is available.

Need help?

If you are seeing crawl failures or 403 errors on your Khoros content source, or are unsure whether CommunityGuard is enabled on your community, raise a ticket with SearchUnify Support and our team will help you through it.

Thanks

Team SearchUnify