Enable Lucidworks crawlers in Adobe Experience Manager as a Cloud Service
This article describes how to configure Lucidworks crawlers to access Adobe Experience Manager as a Cloud Service environments using supported authentication methods.
Description description
Organizations may need to allow Lucidworks crawlers to index content from their Adobe Experience Manager as a Cloud Service environments. Unlike AEM On-Premise, where strong authentication can sometimes be bypassed for specific users or IP addresses, AEM as a Cloud Service doesn’t allow direct modification of OSGi configurations. All integrations, including Lucidworks crawlers, must use supported authentication mechanisms.
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS) (all versions)
Symptoms
Lucidworks crawlers are unable to access AEM as a Cloud Service Publish instances without strong authentication (such as SAML or OAuth).
Cause
AEM as a Cloud Service doesn’t allow bypassing strong authentication via OSGi configuration changes. All integrations must use supported authentication methods.
Resolution resolution
Follow the steps below to resolve the issue:
- Review the official Adobe documentation on generating access tokens for server-side APIs in AEM as a Cloud Service.
- Determine if Lucidworks supports authentication using OAuth or access tokens. If so, configure Lucidworks to use these supported methods for crawling AEM content.
- If Lucidworks doesn’t support OAuth or access tokens, contact Lucidworks support to explore enabling these authentication methods for your crawler integration.
- If your content is intended to be publicly accessible and doesn’t require authentication, review your AEM Publish environment settings to determine if public, unauthenticated access can be safely enabled for the required content. This isn’t recommended for sensitive or restricted content.
- After configuring the appropriate authentication method, verify that Lucidworks is able to successfully crawl the required AEM content.